Amazon Route 53
Scalable DNS and domain name registration service
Route 53 is like the phone book of the internet: when someone types your website name (like example.com), Route 53 translates it into the actual address (IP address) where your website lives. But it's smarter than a regular phone book. It can route people to the closest server (latency-based routing), send traffic to healthy servers only (health checks), or split traffic between multiple servers (weighted routing). It's called Route 53 because DNS uses port 53, and it's a nod to the famous U.S. Route 66, a highway that gets you where you need to go. Route 53 ensures your users always reach your application, even if some servers fail.
Route 53 is a highly available DNS service that translates domain names to IP addresses. You create hosted zones (containers for DNS records) and define records (A, AAAA, CNAME, MX, TXT, etc.). Route 53 supports multiple routing policies: Simple (single resource), Weighted (distribute traffic by percentage), Latency (route to lowest latency endpoint), Failover (active-passive), Geolocation (route by user location), Geoproximity (route by geographic distance with bias), and Multivalue Answer (return multiple IPs with health checks). Health checks monitor endpoint available; Route 53 stops routing to unhealthy endpoints automatically.
Key Capabilities
Key features: domain registration, DNSSEC for security, traffic flow (visual policy editor), and alias records (route to AWS resources like ELB, CloudFront without additional charges).
Gotchas & Constraints
Gotcha #1: DNS changes take time to propagate due to TTL (time-to-live); plan for gradual rollouts. Gotcha #2: Alias records are free for AWS resources, but CNAME records incur charges. Constraints: Route 53 is a global service (not region-specific), and DNS queries are eventually consistent.
A global SaaS company serves customers in North America, Europe, and Asia. They deploy their application in three regions: us-east-1, eu-west-1, and ap-southeast-1. Using Route 53 latency-based routing, they create A records for app.example.com pointing to Application Load Balancers in each region. When a user in Tokyo accesses the site, Route 53 routes them to ap-southeast-1 (lowest latency). When a user in London accesses it, they're routed to eu-west-1. Route 53 health checks monitor each ALB; if us-east-1 fails, Route 53 automatically stops routing traffic there, directing users to the next-closest healthy region. For their API (api.example.com), they use weighted routing to gradually roll out a new version: 90% traffic to the old version, 10% to the new version. After validating the new version, they shift to 100%. Route 53 also manages their domain registration and email (MX records), providing a single service for all DNS needs.