Global Content Delivery.
Edge Security.

📋 How It Works

1. User queries streamflix.com
2. Route 53 returns the IP(s) you configured
3. If multiple IPs → client picks randomly

🏢 Real-World Example

A small company blog hosted on a single EC2 instance with an Elastic IP. No need for complex routing.

📋 How It Works

1. Create 2+ records with the same name
2. Assign weights: v2 = 70, v1 = 30
3. 70% of queries → v2, 30% → v1
4. Set v1 weight = 0 to finish migration

🏢 Real-World Example

Canary deployment: Netflix deploys a new version to 5% of users. If no errors after 1 hour, increase to 50%, then 100%.

📋 How It Works

1. Deploy app in multiple AWS regions
2. Create latency records for each region
3. User's DNS resolver asks Route 53
4. Route 53 checks latency table → picks lowest

🏢 Real-World Example

Amazon.com uses this! Users in India get routed to ap-south-1 (Mumbai), US users to us-east-1. Reduces page load time by 200ms+.

📋 How It Works

1. Create a health check for primary endpoint
2. Primary record → Failover type = PRIMARY
3. Secondary record → Failover type = SECONDARY
4. Health check fails 3x → Route 53 switches to secondary
5. Primary recovers → Route 53 switches back

🏢 Real-World Example

Banking website: Primary in us-east-1, standby in eu-west-1. If Virginia goes down (like the 2017 S3 outage), customers automatically hit Ireland. Zero downtime.

📋 How It Works

1. Create records with location rules:
   • Country = Japan → Tokyo ALB
   • Continent = Europe → Ireland ALB
   • Default → Virginia ALB
2. Route 53 detects user's country from DNS resolver IP
3. Matches the most specific rule first

🏢 Real-World Example

Netflix content licensing: "Squid Game" is available in Korea but not in the US. Geo-routing ensures Korean users see Korean content library, US users see US library.

GDPR compliance: EU users are routed to EU-based servers that comply with European data laws.

📋 How It Works

1. Create 8 A records, each with its own health check
2. Route 53 checks health of all 8
3. Returns only healthy ones (up to 8)
4. Client picks one randomly

🏢 Real-World Example

Small startup with 4 web servers and no budget for an ALB ($16/month). Use Multivalue to spread traffic and auto-remove bad servers from DNS.

📋 How It Works

1. Open Route 53 → Traffic Flow → Create policy
2. Add resources with lat/long or AWS region
3. Adjust bias (−99 to +99)
4. Positive bias = larger area = more traffic
5. Negative bias = smaller area = less traffic

🏢 Real-World Example

Expanding into a new market: You launch Mumbai servers but want to gradually shift Middle East traffic from Ireland → Mumbai. Increase Mumbai bias from 0 → +25 → +50 over weeks.

📋 How It Works

1. Create a CIDR collection in Route 53
2. Add CIDR blocks (e.g., 203.0.113.0/24)
3. Associate CIDR blocks with DNS records
4. Route 53 matches client IP → routes to matched record

🏢 Real-World Example

Telecom company: Jio users (specific IP ranges) are routed to Mumbai CDN, Airtel users to a different CDN. Optimizes peering and reduces inter-ISP transit costs.