The same web service runs in several Regions.
Reduce user network latency and connect to a healthy regional endpoint.
Which routing policy is most appropriate?
Use Route 53 latency-based routing to return the endpoint expected to have the lowest latency for the user.
Detailed explanation
Route 53 can return the Region expected to provide the lowest latency.
Route 53 can return the Region expected to provide the lowest latency.
S3 Lifecycle manages objects and does not provide DNS routing.
S3 Lifecycle manages objects and does not provide DNS routing.
A single address cannot select a Region based on user location and latency.
A single address cannot select a Region based on user location and latency.
IAM manages API permissions, not DNS endpoint selection.
IAM manages API permissions, not DNS endpoint selection.
Check official documentation
Compare the following points with the official documentation.
Route 53 latency-based routingの公式説明を確認する。
What to confirm
レイテンシーを基準にしたDNSルーティングを説明できる。
Key points
- Route 53
- Latency-based routing
- Multi-Region
Notes
- Environment: AWS公式Route 53ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
DNS selection
Route 53 chooses an answer; it does not move application data between Regions.
Health integration
Health checks can prevent an unavailable endpoint from being returned.