AWS Certified Solutions Architect – Associate
Route 53 routing policies: failover, weighted, latency, geo
The routing policy decides how Route 53 answers a DNS query. Failover gives active-passive, weighted splits traffic by proportion, latency picks the AWS Region with the lowest latency, geolocation goes by where the user is, geoproximity by distance with an adjustable bias, and multivalue returns up to eight healthy records at random.
The policies
Simple: one resource for the name. Failover: active-passive. Weighted: traffic in proportions you set; a record's share is its weight divided by the sum of the weights. Latency: resources in several AWS Regions, answer from the Region with the best latency for the user, based on measured AWS latency data that changes over time.
Geolocation: route by the user's continent, country or US state. The smallest matching region wins. Queries from unmapped IPs or locations without a record get no answer unless you create a default record.
Geoproximity: route by the location of users and resources. A bias from 1 to 99 expands the area a resource serves; -1 to -99 shrinks it. IP-based: route by the source IP ranges you know. Multivalue answer: up to eight healthy records selected at random.
Health checks and failover
Active-passive uses the failover policy: Route 53 answers with the primary while it is healthy and with the secondary when it is not. Active-active uses any other policy with health checks; Route 53 drops unhealthy records from answers.
For alias records to AWS resources such as load balancers, set Evaluate Target Health to Yes instead of creating a health check. An alias to an S3 website endpoint must have a record name that matches the bucket name.
In a weighted group, zero-weight records are used only when every nonzero record is unhealthy. If every record in a group is unhealthy, Route 53 treats them all as healthy and still answers, rather than returning no answer.
Multivalue is not a load balancer
Multivalue answer routing lets you attach a health check to each record so only healthy IPs are returned. AWS says it is not a substitute for a load balancer, but it improves uptime and spreads load through DNS.
Where the exam catches people
- Believing latency routing picks the geographically nearest Region: it uses measured latency data, which changes over time.
- Believing geolocation sends unmatched users to the nearest record: without a default record, Route 53 returns no answer for them.
- Believing Route 53 returns nothing when every record is unhealthy: it reverts to treating all records as healthy and answers anyway.
- Believing a positive geoproximity bias shrinks a resource's area: positive expands it, negative shrinks it.
- Believing a simple record with several IPs removes failed servers: only health-checked records, such as multivalue, drop unhealthy values.