Routing Policies

Traffic Management and Load Distribution

Simple Routing

Returns a single resource record for a DNS query. Use when you have one resource performing a function.

One record per name
No health checks
Most basic routing policy

Weighted Routing

Route traffic to multiple resources in proportions you specify. Useful for load balancing and testing.

Assign weights 0-255
Traffic % = weight/total weights
A/B testing and gradual rollouts

Latency-Based

Route traffic based on lowest network latency for your end user to the AWS region.

Measures latency to AWS regions
Routes to lowest latency region
Improves user experience

Geolocation

Route traffic based on the geographic location of your users (continent, country, or state).

Based on user location
Content localization
Compliance requirements

Failover Routing

Primary Resource

Active resource that handles traffic when healthy

Secondary Resource

Standby resource used when primary fails health check

Routing Policies Exam Tips

  • • Simple routing: one resource, no health checks
  • • Weighted routing: distribute traffic by percentage
  • • Latency-based: route to lowest latency AWS region
  • • Geolocation: route based on user's geographic location
  • • Failover: requires health checks for primary/secondary setup
Previous: Hosted Zones Next: Health Checks