Ensure CloudFront distributions have origin failover configured for critical applications
Origin failover automatically switches to secondary origin when primary origin is unavailable, improving application availability and resilience.
Security Impact
Without origin failover, primary origin failures result in complete service outages instead of automatic failover.
How to Remediate
Create origin groups with primary and secondary origins. Configure failover criteria based on HTTP status codes.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Amazon CloudFront resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, High Availability, Business Continuity compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudfront-12
- Service
- Amazon CloudFront
- Category
- High Availability
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon CloudFront Checks
View all checksEnsure CloudFront distributions use secure SSL/TLS protocols
Ensure CloudFront distributions enforce HTTPS-only viewer connections
Ensure CloudFront distributions use origin access identity (OAI) for S3 origins
Ensure CloudFront distributions have access logging enabled
Ensure CloudFront distributions have WAF integrated