When a primary-Region endpoint is unavailable, DNS should direct users to a site in another Region.
Switch automatically based on endpoint health.
Which design is most appropriate?
Route 53 health checks and failover routing can return the primary or secondary endpoint according to health status.
Detailed explanation
Route 53 can select the primary or secondary DNS answer based on health-check results.
Route 53 can select the primary or secondary DNS answer based on health-check results.
KMS key management is unrelated to DNS failover.
KMS key management is unrelated to DNS failover.
A cache TTL controls freshness and is not a health-check-based DNS switch.
A cache TTL controls freshness and is not a health-check-based DNS switch.
IAM manages permissions and does not perform DNS routing or health checks.
IAM manages permissions and does not perform DNS routing or health checks.
Check official documentation
Compare the following points with the official documentation.
Amazon Route 53のヘルスチェックとフェイルオーバールーティングの公式説明を確認する。
What to confirm
DNSレベルの障害検知とセカンダリへの切り替えを設計できる。
Key points
- Amazon Route 53
- Health check
- Failover routing
- DNS response
Notes
- Environment: AWS公式Route 53ドキュメントの確認
- Confirm current AWS architecture guidance and service behavior in the official documentation.
Foundation review
Detection and routing
Route 53 combines health observations with routing policy to change the DNS answer.
Cache timing
DNS and CDN cache freshness are different mechanisms from active endpoint health checks.