Route 53 Routing Policies: What It Is and When to Use It

Definition

Amazon Route 53 Routing Policies are sets of rules within the AWS Domain Name System (DNS) service that determine how Route 53 responds to DNS queries. They allow developers and architects to control how internet traffic is directed to application endpoints, solving for complex requirements like high availability, low latency, and geographically targeted content delivery.

How It Works

When a user initiates a DNS query for a domain managed by Route 53, the service evaluates the record sets in the corresponding hosted zone. Each record set is configured with a specific routing policy. This policy dictates which IP address or domain name Route 53 returns to the user, based on conditions such as the user's location, the health of the endpoint, or pre-defined weights.

For example, a Latency-based policy will cause Route 53 to return the IP address of the AWS region with the lowest network latency for that specific user. A Failover policy will return the IP of a primary resource, but if its health check fails, Route 53 will automatically start returning the IP of a secondary, standby resource. This decision-making happens at the DNS layer, before any direct traffic is sent to the application itself.

Key Features and Limits

Route 53 offers several distinct routing policies, each designed for different traffic management scenarios.

• Simple Routing: The most basic policy, used to route traffic to a single resource, like a web server. It does not support health checks.
• Weighted Routing: Distributes traffic across multiple resources in proportions that you define (e.g., 80% to one fleet, 20% to another). This is ideal for A/B testing and canary deployments.
• Latency-Based Routing: Routes users to the AWS region that provides the lowest network latency. This is effective for global applications where performance is critical.
• Failover Routing: Used to configure an active-passive failover. Route 53 directs traffic to a primary resource and switches to a secondary (standby) resource if the primary becomes unhealthy, as determined by Route 53 Health Checks.
• Geolocation Routing: Routes traffic based on the geographic location of the user (continent, country, or US state). This is used for content localization, and enforcing geographic restrictions.
• Geoproximity Routing: Routes traffic based on the geographic location of both your users and your resources. It includes an optional "bias" feature to expand or shrink the geographic area from which traffic is routed to a resource. This policy requires the use of Route 53 Traffic Flow.
• Multivalue Answer Routing: Responds to DNS queries with up to eight healthy records selected at random. This provides a simple way to distribute traffic and improve availability, as Route 53 will only return records for healthy endpoints.
• IP-Based Routing: Routes traffic based on the user's source IP address or CIDR block. This allows for highly granular traffic management, such as routing traffic from a corporate network differently than public traffic.

Service Limits (Quotas):

• Hosted Zones: 500 per AWS account (can be increased).
• Records per Hosted Zone: 10,000 (can be increased).
• Health Checks: 200 per AWS account (can be increased).
• API Request Rate: 5 requests per second per AWS account, which can be a limitation for large-scale automation.

Common Use Cases

• High Availability and Disaster Recovery: Using Failover routing with health checks to automatically direct users to a secondary region or a static S3 website if the primary application endpoint fails.
• A/B Testing and Canary Releases: Using Weighted routing to send a small percentage of traffic (e.g., 5%) to a new application version while the majority of users continue to use the stable version.
• Global Performance Optimization: Using Latency-based routing for a worldwide application deployed across multiple AWS regions, ensuring users are always served from the region with the fastest response time.
• Localized Content Delivery: Using Geolocation routing to serve different versions of a website (e.g., in different languages or with different product pricing) based on the user's country.
• DNS-Level Load Balancing: Using Multivalue Answer routing with health checks to distribute traffic across a small fleet of web servers without needing a dedicated Elastic Load Balancer (ELB).

Pricing Model

Amazon Route 53 pricing is pay-as-you-go and has several components:

• Hosted Zones: A monthly charge per hosted zone managed by Route 53 (e.g., $0.50 per month for the first 25 zones).
• DNS Queries: You pay per million queries. The price varies by routing policy type; Standard queries (Simple, Weighted, Failover, Multivalue) are the least expensive, while Latency-based and Geolocation queries cost more. Queries to Alias records pointing to AWS resources like ELBs, CloudFront distributions, and S3 buckets are free.
• Health Checks: There is a monthly charge per health check. The first 50 health checks for AWS endpoints are free. Checks against non-AWS endpoints cost more, and optional features like latency measurement add to the cost.
• Traffic Flow: There is a significant monthly charge per policy record created using the Traffic Flow visual editor.

For detailed and current pricing, always refer to the official AWS Route 53 pricing page and the AWS Pricing Calculator.

Pros and Cons

Pros:

• High Availability: Route 53 is built on a globally distributed network of DNS servers, offering a 100% availability Service Level Agreement (SLA).
• Scalability: Automatically scales to handle massive query volumes without manual intervention.
• Flexibility: A wide range of routing policies covers most common and many advanced traffic management patterns.
• AWS Integration: Tightly integrated with other AWS services like ELB, S3, and CloudFront through special "Alias" records, which offer free queries and simplified management.

Cons:

• DNS Propagation and Caching: As a DNS-based service, changes can take time to propagate globally due to the nature of DNS caching. This can delay failover events compared to network-level solutions.
• Complexity: Advanced features like Geoproximity routing require using the more complex and expensive Traffic Flow feature.
• API Rate Limiting: The default API request limit of 5 requests per second can be a bottleneck for infrastructure-as-code (IaC) tools like Terraform managing a large number of records.

Comparison with Alternatives

• Route 53 vs. Elastic Load Balancing (ELB): Route 53 operates at the DNS layer to direct clients to an endpoint (like an ELB or an EC2 instance). ELB operates at the transport/application layer to distribute incoming traffic across a fleet of targets within a region. They are often used together: Route 53 provides global routing to the correct regional ELB, and the ELB then handles local load balancing.

• Route 53 (Latency Routing) vs. AWS Global Accelerator: Both services route users to the optimal AWS endpoint. However, Route 53 makes this decision via DNS resolution. Global Accelerator provides static Anycast IP addresses that route traffic over the AWS global network backbone from an edge location close to the user, which can reduce latency and improve reliability compared to routing over the public internet. Global Accelerator is often faster for failover as it is not dependent on DNS TTLs.

Exam Relevance

Amazon Route 53 and its routing policies are a core topic on several AWS certification exams, particularly:

• AWS Certified Solutions Architect - Associate (SAA-C03): Expect scenario-based questions asking you to choose the most appropriate routing policy to meet a specific requirement (e.g., disaster recovery, blue/green deployment, latency reduction).
• AWS Certified Developer - Associate (DVA-C02): Knowledge of routing policies is relevant for deploying highly available and scalable applications.
• AWS Certified SysOps Administrator - Associate (SOA-C02): Focuses on operational aspects, such as implementing failover configurations and monitoring with health checks.

Examinees must know the use case for each policy and understand the difference between options like Latency and Geolocation, and Failover and Multivalue Answer.

Frequently Asked Questions

Q: What is the difference between Latency-based routing and Geolocation routing?

A: Latency-based routing directs users to the AWS region with the lowest network latency for them, regardless of their physical location. Geolocation routing directs users based on their actual geographic location (e.g., country or continent), which is used for serving localized content or enforcing data sovereignty, not necessarily for the best performance.

Q: How do Route 53 Health Checks work with Failover routing?

A: For a Failover routing policy, you configure a health check on your primary endpoint. Route 53 periodically sends requests to that endpoint to verify its health. If the health check fails a configured number of times, Route 53 marks the endpoint as unhealthy and automatically starts responding to DNS queries with the address of your designated secondary (failover) endpoint.

Q: Can I use multiple routing policies for the same domain?

A: Yes, you can combine routing policies using Route 53 Traffic Flow, which provides a visual editor to build sophisticated routing configurations. For example, you could create a policy that first uses Geolocation routing to send users from Europe to a specific set of endpoints, and then uses Latency-based routing to direct them to the lowest-latency endpoint within that European set.

---

This article reflects AWS features and pricing as of 2026. AWS services evolve rapidly — always verify against the official AWS documentation before making production decisions.