LOW

Ensure CloudFront distributions use HTTP/2 or HTTP/3

HTTP/2 and HTTP/3 provide significant performance improvements through multiplexing, header compression, and reduced latency compared to HTTP/1.1.

Security Impact

HTTP/1.1-only distributions provide slower page loads and inferior user experience compared to modern protocols.

How to Remediate

Enable HTTP/2 and HTTP/3 in CloudFront distribution settings. These are enabled by default for new distributions.

Affected Resources

AWS::CloudFront::Distribution

Compliance Frameworks

Performance Best Practices

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 Performance Best Practices compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-cloudfront-15
Service
Amazon CloudFront
Category
Performance
Severity
LOW

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Amazon CloudFront Checks

View all checks
aws-cloudfront-1high

Ensure CloudFront distributions use secure SSL/TLS protocols

aws-cloudfront-2high

Ensure CloudFront distributions enforce HTTPS-only viewer connections

aws-cloudfront-3high

Ensure CloudFront distributions use origin access identity (OAI) for S3 origins

aws-cloudfront-4medium

Ensure CloudFront distributions have access logging enabled

aws-cloudfront-5high

Ensure CloudFront distributions have WAF integrated