All Services

Networking & CDN

Amazon Route 53

Amazon Route 53 provides authoritative public DNS, private hosted zones, domain registration, health checks, traffic-flow policies, DNSSEC, Resolver endpoints and rules, query logging, and application recovery controls.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Route 53.

Amazon Route 53 pricing and cost programs

Pricing model: DNS and routing usage

On-Demand
Available
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Hosted zones · DNS queries · Health checks · Resolver endpoints and queries

Programs and modes: Public and private DNS · Traffic Flow · Resolver · Domains

Domain-registration charges and optional routing features are separate from query charges.

Free Tier: Service-specific — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Route 53?

  • Provides globally available authoritative DNS and AWS-resource aliases without operating name servers.
  • Supports simple, weighted, latency, failover, geolocation, geoproximity and multivalue routing with health evaluation.
  • Combines public and private DNS, hybrid Resolver endpoints, DNSSEC, query logging, domain controls, and recovery features.

How to implement Amazon Route 53

  1. Define domain and subdomain ownership, registrar protection, delegation, public and private namespaces, split-horizon behavior, TTL objectives, record automation, hybrid resolution, and disaster-recovery authority.
  2. Create hosted zones and least-privilege change roles, prefer alias records for supported AWS targets, choose a default routing answer, add health checks or target-health evaluation only where failover is actionable, and enable DNSSEC when operationally supported.
  3. Wait for and verify change completion, test public and private resolvers from real clients, simulate unhealthy endpoints and Region loss, monitor query and health metrics, and inventory stale zones, records, domains and Resolver rules.

Amazon Route 53 best practices

  • Use TTLs that balance resolver efficiency with required change speed, remembering that resolvers cache failures and old answers; shorten TTL before planned migrations, then restore it.
  • Prefer aliases over CNAMEs for supported AWS resources, always define a safe default routing record, and avoid cyclic Resolver forwarding or single-AZ inbound endpoints.
  • Protect registrar and hosted-zone changes with MFA, least privilege, DNSSEC and audit trails; do not assume an HTTPS health check validates the endpoint certificate because Route 53 health checks do not.

Amazon Route 53 use cases and server impact

  • Public and private application DNS
  • Health-aware multi-Region routing
  • Hybrid DNS forwarding and domain registration

Replaces authoritative DNS and much health-aware routing infrastructure, while namespace ownership, registrar security, TTL strategy, endpoint health semantics, hybrid resolution, and recovery testing remain yours.

Official implementation resources

Commonly paired AWS services

Architecture patterns using this service