Opscraft
AWS cloud

Route 53 routing policies

Must-know10 lessons · 32 min · 3 tests ·

Route 53 routing policies decide which answer a DNS query gets: split traffic by weight, send users to the lowest-latency region, fail over to a standby, route by the user's country or network. Combined with health checks, they're the backbone of multi-region and disaster-recovery designs on AWS. Senior interviews expect you to know all eight policies, how health checks drive them, how to nest policies for real architectures, and — crucially — the limits of DNS-based traffic management.

Stage 2 · Core tools

Know these first

After this topic you can

  • Choose a routing policy (weighted, latency, failover, geolocation)
  • Combine policies with health checks for failover
  • Plan blue/green and regional traffic shifts with DNS

Lessons

  1. 1How routing policies work 4 min read
    • Record sets with set identifiers
    • The eight policies
    • Health checks + evaluate target health
    • TTL is always in play
  2. 2Simple and multivalue answer 3 min read
    • Simple
    • Multivalue answer
  3. 3Weighted routing 3 min read
    • How weights work
    • Uses
    • Why weighted DNS is imprecise for canaries
  4. 4Latency-based routing 3 min read
    • How it decides
    • Caveats
  5. 5Failover routing 3 min read
    • Active-passive
    • Failover timing
    • "Failover isn't switching even though the primary is down"
  6. 6Geolocation, geoproximity and IP-based routing 3 min read
    • Geolocation
    • Geoproximity (Traffic Flow)
    • IP-based routing
    • Latency vs geolocation in one line
  7. 7Health checks in depth 3 min read
    • Types
    • Settings
    • Design a meaningful health endpoint
    • Flapping
    • Cost
  8. 8Combining policies and real designs 3 min read
    • Nesting with aliases
    • Design: global app with EU data residency
    • Design: active-passive DR with a maintenance page
    • Design: migrate traffic to a new account/stack
    • Design: route a customer by office IPs
    • Testing before go-live
  9. 9Limits of DNS-based traffic management 3 min read
    • What DNS can't do
    • Complementary AWS services
  10. 10Interview questions and model answers 4 min read
    • "Name the Route 53 routing policies and when you'd use each."
    • "Latency vs geolocation routing?"
    • "Why not use weighted DNS for a 5% canary?"
    • "Failover isn't happening although the primary is down. What do you check?"
    • "How would you health-check a private endpoint?"
    • "Design global routing: EU users must stay in the EU, everyone else should get the fastest region, with failover."
    • "Can you fail over a database with Route 53?"
    • "Which routing policy have you used and why?" (how to answer)