📡 You're offline — showing cached content
New version available!
Quick Access
Tutorials AWS Solutions Architect Route 53 — DNS and Traffic Routing

Route 53 — DNS and Traffic Routing

5 min read Quiz at the end
Master Route 53 routing policies (latency, failover, geolocation, weighted) and how CloudFront CDN accelerates global content delivery.

Route 53 — DNS and Intelligent Traffic Routing

Route 53 is AWS's DNS service — it translates domain names (www.example.com) into IP addresses. But it does much more: it intelligently routes traffic globally, performs health checks, and enables automatic failover.

Teacher Note: DNS is like a phone book for the internet. When you type www.google.com, DNS looks up and returns the actual IP address (142.250.80.46). Route 53 is AWS's phone book — but a SMART one that can send different users to different servers based on their location, speed, or server health.

Route 53 Routing Policies

PolicyWhat it DoesUse Case
SimpleOne record — one IP addressBasic websites, single server
WeightedSend 10% to server A, 90% to server BA/B testing, gradual deployments
Latency-basedRoute to the FASTEST region for each userGlobal apps needing low latency
FailoverActive/Passive — switch to backup if primary failsDisaster recovery
GeolocationRoute based on user's COUNTRY or CONTINENTData sovereignty, localisation
GeoproximityRoute based on distance — adjustable biasFine-grained global traffic control
Multi-Value AnswerReturn multiple healthy IPsSimple load balancing with health checks

CloudFront — Content Delivery Network (CDN)

CloudFront caches your content at 400+ edge locations worldwide. Users download content from the nearest edge location, not your origin server — dramatically reducing latency.

Without CloudFront:
  User in Mumbai --> Server in US (200ms latency)

With CloudFront:
  User in Mumbai --> Edge Location in Mumbai (5ms latency)
FeatureWhat it Does
OriginWhere CloudFront fetches content: S3 bucket, ALB, EC2, custom HTTP server
Cache BehaviourRules for how long to cache different URL paths
Origin Access Control (OAC)Makes S3 bucket PRIVATE — only CloudFront can access it
Lambda@EdgeRun code at the edge for authentication, URL rewriting, personalisation
WAF IntegrationBlock malicious requests before they reach your origin
Exam Tip: CloudFront + S3 + OAC is a favourite exam combo. OAC (Origin Access Control) restricts S3 bucket to ONLY allow CloudFront — users cannot bypass CloudFront to access S3 directly. This adds security AND forces all traffic through WAF and caching.
Topic Quiz · 2 questions

Test your understanding before moving on

1. A global application needs to route each user to the AWS region that gives them the fastest response. Which Route 53 routing policy should be used?
💡 Latency-based routing measures actual network latency to each region and routes users to the fastest option.
2. A company wants to host a static website on S3 but ensure users CANNOT access S3 directly — only through CloudFront. What feature enables this?
💡 Origin Access Control (OAC) makes the S3 bucket private and only allows CloudFront to access it — users cannot bypass CloudFront.