Amazon Route 53 & Routing Policies
Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. It is designed to give developers and businesses an extremely reliable and cost-effective way to route end users to Internet applications by translating names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other.
The “Global Switchboard” Analogy
Imagine Route 53 as a Global Switchboard Operator. When a customer (User) picks up the phone to call a business (Your Website), the operator doesn’t just give them one number. Depending on who is calling, where they are calling from, or if some office branches are currently closed for maintenance, the operator directs the call to the specific desk (Server/Region) that can best handle the request at that exact moment.
Core Concepts & Well-Architected Framework
Reliability (The 100% SLA)
Route 53 is one of the few AWS services that offers a 100% Availability Service Level Agreement. It achieves this through a global network of redundant DNS servers located in AWS Edge Locations worldwide.
Performance Efficiency
By using Latency-based routing, Route 53 ensures that users are directed to the AWS Region that provides the lowest network latency, significantly improving the user experience for global applications.
Routing Policy Comparison
| Policy | Best For… | Key Characteristic |
|---|---|---|
| Simple | Single resource environments. | Standard DNS; one record with multiple IP addresses (randomized). |
| Weighted | Blue/Green deployments & Canary testing. | Assign relative weights (e.g., 90% to V1, 10% to V2). |
| Latency | Performance-critical global apps. | Routes to the region with the lowest round-trip time. |
| Failover | Disaster Recovery (DR). | Active-Passive setup; switches to secondary if health check fails. |
| Geolocation | Compliance and Localized Content. | Routes based on user’s physical location (State/Country). |
| Multi-Value Answer | High availability with client-side load balancing. | Returns up to 8 healthy records; similar to Simple but with Health Checks. |
Scenario-Based Learning: Decision Matrix
- IF you need to test a new software version with only 5% of traffic THEN use Weighted Routing.
- IF you must ensure users in the EU are served from the Frankfurt region for GDPR THEN use Geolocation Routing.
- IF you want to minimize the impact of a regional outage THEN use Failover Routing.
- IF you have multiple resources and want to return several IPs to the client for redundancy THEN use Multi-Value Answer.
Exam Tips: Golden Nuggets
- Alias vs CNAME: Always choose Alias Records for AWS resources (ELB, S3 buckets). Unlike CNAMEs, Alias records are free and can be used for the “Zone Apex” (e.g., example.com without the ‘www’).
- Health Checks: Route 53 can check the health of an endpoint. If the endpoint is unhealthy, Route 53 stops routing traffic to it. Note: Simple routing does NOT support health checks.
- TTL (Time To Live): Lower TTL means faster propagation of changes but higher cost (more DNS queries). Higher TTL means lower cost but slower updates.
- Private Hosted Zones: Used for internal VPC resources. Requires
enableDnsHostnamesandenableDnsSupportset to true in the VPC.
Visual Traffic Flow
Route 53 evaluates Health Checks before sending traffic to regional endpoints.
Key Services
- Public Hosted Zones: Accessible from the internet.
- Private Hosted Zones: Restricted to your VPCs.
- Resolver: Hybrid cloud DNS queries (On-prem to AWS).
Common Pitfalls
- Trying to use a CNAME for the root domain (use Alias!).
- Forgetting that Simple Routing doesn’t support Health Checks.
- Not configuring Health Checks for Failover policies.
Quick Patterns
- Active-Active: Weighted or Latency routing.
- Active-Passive: Failover routing.
- Global Expansion: Geoproximity with bias.