The same web service runs in multiple Regions.
Direct each user to the Region that offers the lowest network latency.
Which Route 53 policy is most appropriate?
Use Route 53 latency-based routing to return the Region with the lowest measured latency for the requesting user.
Detailed explanation
IAM handles authorization and does not measure or route DNS requests by latency.
IAM handles authorization and does not measure or route DNS requests by latency.
Latency-based routing selects the endpoint in the Region that has the lowest latency for the user.
Latency-based routing selects the endpoint in the Region that has the lowest latency for the user.
S3 lifecycle rules do not select a DNS response based on user latency.
S3 lifecycle rules do not select a DNS response based on user latency.
A single fixed destination does not compare latency among Regions.
A single fixed destination does not compare latency among Regions.
Check official documentation
Compare the following points with the official documentation.
Amazon Route 53 latency-based routingの公式説明を確認する。
What to confirm
複数リージョンの名前解決とレイテンシー要件を対応付けられる。
Key points
- Latency-based routing
- Amazon Route 53
- Multi-Region
Notes
- Environment: AWS公式Route 53ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Performance versus failover
Latency-based routing addresses speed; health checks and failover policies address endpoint availability.
DNS decision
Route 53 chooses the response, but the application still needs regional data and failure handling.