Ensure CloudFront distributions enforce HTTPS-only viewer connections
CloudFront distributions should redirect HTTP requests to HTTPS or block them entirely to prevent man-in-the-middle attacks and data interception.
Security Impact
HTTP connections transmit data in clear text, allowing network eavesdropping and session hijacking attacks.
How to Remediate
Set Viewer Protocol Policy to 'Redirect HTTP to HTTPS' or 'HTTPS Only' for all cache behaviors in the distribution.
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 PCI-DSS, HIPAA, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudfront-2
- Service
- Amazon CloudFront
- Category
- Encryption
- Severity
- HIGH
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 use origin access identity (OAI) for S3 origins
Ensure CloudFront distributions have access logging enabled
Ensure CloudFront distributions have WAF integrated
Ensure CloudFront distributions use field-level encryption for sensitive data