A CloudFront distribution normally uses an ALB.
For selected HTTP errors, serve a static page from an S3 origin.
Which configuration is most appropriate?
Configure a CloudFront origin group with primary and secondary origins and an origin-failover status-code policy.
Detailed explanation
S3 lifecycle management does not change a CloudFront origin.
S3 lifecycle management does not change a CloudFront origin.
DNS routing does not configure failover between origins inside a CloudFront distribution.
DNS routing does not configure failover between origins inside a CloudFront distribution.
An origin group switches to the secondary origin for the configured failure responses.
An origin group switches to the secondary origin for the configured failure responses.
Cache lifetime does not define an origin failover path.
Cache lifetime does not define an origin failover path.
Check official documentation
Compare the following points with the official documentation.
CloudFront origin failoverの公式説明を確認する。
What to confirm
DNSフェイルオーバーとCloudFrontオリジンフェイルオーバーを区別できる。
Key points
- CloudFront origin group
- Primary origin
- Secondary origin
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Distribution-level failover
Origin failover is different from changing DNS records for separate distributions.
Error policy
Only selected origin responses should trigger a switch, so normal application errors remain visible when appropriate.