Route 53 health checks cost: the small fees behind DNS failover

Quick answer

Route 53 health checks cost $0.50 per month each for endpoints within AWS and $0.75 per month each for endpoints outside AWS. Optional features add on top: HTTPS, string matching, fast interval (every 10 seconds instead of 30), and latency measurement each add about $1 to $2 per month per check. So a basic AWS health check is $0.50, but a fast-interval HTTPS check with string matching on an external endpoint can approach $3 to $4 per month. Individually trivial, but the fees compound: fifty health checks with add-ons can be $150 or more a month, so audit which checks and features you actually need.

Route 53 health checks power DNS failover, routing traffic away from unhealthy endpoints. They are cheap enough that most teams ignore their cost, and usually that is fine. But the pricing has several layers, AWS versus external endpoints, plus optional features that each carry their own fee, and at scale a fleet of feature-rich health checks becomes a line item worth understanding.

The base rates

Health check type	Monthly cost
AWS endpoint	$0.50 each
External (non-AWS) endpoint	$0.75 each

A health check monitoring an endpoint within AWS (identified by AWS resource) costs $0.50 per month. A health check monitoring an endpoint outside AWS, by IP or domain, costs $0.75 per month. That difference reflects AWS monitoring its own infrastructure more cheaply than external targets.

The optional feature fees

Feature	Approximate added cost
HTTPS	~$1/mo per check
String matching	~$1/mo per check
Fast interval (10s)	~$1/mo per check
Latency measurement	~$1/mo per check

Each optional feature adds roughly $1 to $2 per month per check. HTTPS monitoring, checking response body content with string matching, using the fast 10-second interval instead of the default 30 seconds, and measuring latency each cost extra. Stack several onto one external check and its monthly cost can reach $3 to $4, six to eight times the base AWS rate.

Where the total grows

The cost problem is never one health check, it is scale. A large environment monitoring dozens of endpoints, each with HTTPS and fast intervals, adds up. Fifty external checks at $0.75 each is $37.50, and adding HTTPS and fast interval to all of them pushes past $150 a month. Combine that with the hosted zone fees of $0.50 per zone and the query charges of $0.40 per million, covered in theRoute 53 cost guide, and DNS becomes a small but real recurring spend.

Keeping health check cost sensible

Audit your health checks periodically and delete ones for endpoints that no longer exist, a common source of waste since a deleted service often leaves its check behind. Use the fast 10-second interval only where rapid failover genuinely matters, since the default 30 seconds is free of that add-on and adequate for most endpoints. Enable HTTPS and string matching only where the deeper check is needed, not by default. And prefer AWS-endpoint checks over external ones where the target is inside AWS, saving the higher external rate.

Health check fees are minor individually but real in aggregate, and they are easy to over-provision with features you do not need. Price your DNS configuration against theresource catalog so the health check and feature fees are counted before you create fifty of them.

FAQ

How much do Route 53 health checks cost?

$0.50 per month each for endpoints within AWS and $0.75 per month each for endpoints outside AWS. Optional features add roughly $1 to $2 per month per check: HTTPS, string matching, the fast 10-second interval, and latency measurement each cost extra. A basic AWS check is $0.50, but a fast-interval HTTPS check with string matching on an external endpoint can approach $3 to $4 a month.

Why are some Route 53 health checks more expensive?

Two reasons: external endpoints cost $0.75 versus $0.50 for AWS endpoints, and optional features each add a fee. HTTPS monitoring, string matching on the response body, the fast 10-second check interval, and latency measurement each add about $1 to $2 per month. Stacking several features onto an external check multiplies its cost several times over the base rate.

Do Route 53 health checks add up at scale?

Yes. One check is trivial, but a large environment monitoring dozens of endpoints with HTTPS and fast intervals adds up. Fifty external checks at $0.75 is $37.50, and adding HTTPS and fast interval to all of them pushes past $150 a month. Combined with hosted zone and query fees, DNS becomes a small but real recurring spend worth auditing.

How do I reduce Route 53 health check cost?

Audit and delete checks for endpoints that no longer exist, a common source of waste. Use the fast 10-second interval only where rapid failover truly matters, since the default 30 seconds avoids that add-on. Enable HTTPS and string matching only where the deeper check is needed. And prefer AWS-endpoint checks over external ones where the target is inside AWS to save the higher external rate.

Is the fast health check interval worth it?

Only where rapid failover genuinely matters. The fast 10-second interval detects failures sooner than the default 30 seconds but adds about $1 a month per check. For critical endpoints where seconds of downtime are costly, it is worth it; for the many endpoints where 30-second detection is adequate, the default saves the add-on across a large fleet of checks.

How does C3X help with Route 53 cost?

C3X prices your Route 53 configuration from Terraform before you deploy, including health checks and their feature options, so the DNS cost is visible in the pull request. That helps you see the aggregate cost of a large health check fleet with add-ons at design time, and avoid over-provisioning features like fast intervals and HTTPS on checks that do not need them.

What to do next

Price your Route 53 health checks before you create them. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.