Skip to main content
MEDIUMCloudFrontSecurity

CloudFront TLS Outdated

cloudfront-tls-outdated

What this rule checks

Detects CloudFront distributions using outdated TLS versions.

How to fix it

  1. 1Set MinimumProtocolVersion to TLSv1.2_2021 or higher
  2. 2Use a custom SSL certificate
FlaggedA custom ACM viewer certificate is attached with minimumProtocolVersion set to TLSv1, which is on the check's outdated list (SSLv3, TLSv1, TLSv1_2016, TLSv1.1_2016). A custom certificate with the version omitted also flags, because it falls back to the old TLSv1 CloudFront default.
import * as cloudfront from 'aws-cdk-lib/aws-cloudfront';
import * as origins from 'aws-cdk-lib/aws-cloudfront-origins';
import * as acm from 'aws-cdk-lib/aws-certificatemanager';

const cert = new acm.Certificate(this, 'Cert', { domainName: 'example.com', validation: acm.CertificateValidation.fromDns() });
new cloudfront.Distribution(this, 'Dist', {
  defaultBehavior: { origin: new origins.HttpOrigin('origin.example.com') },
  domainNames: ['example.com'],
  certificate: cert,
  minimumProtocolVersion: cloudfront.SecurityPolicyProtocol.TLS_V1,
});
FixedTLSv1.2_2021 (SecurityPolicyProtocol.TLS_V1_2_2021) is a modern policy that is not on the outdated list, so the check passes.
import * as cloudfront from 'aws-cdk-lib/aws-cloudfront';
import * as origins from 'aws-cdk-lib/aws-cloudfront-origins';
import * as acm from 'aws-cdk-lib/aws-certificatemanager';

const cert = new acm.Certificate(this, 'Cert', { domainName: 'example.com', validation: acm.CertificateValidation.fromDns() });
new cloudfront.Distribution(this, 'Dist', {
  defaultBehavior: { origin: new origins.HttpOrigin('origin.example.com') },
  domainNames: ['example.com'],
  certificate: cert,
  minimumProtocolVersion: cloudfront.SecurityPolicyProtocol.TLS_V1_2_2021,
});

CDK Insights pinpoints the exact file and line in your CDK source for every finding, so you can jump straight to the fix.

Affected resource types

AWS::CloudFront::Distribution

Compliance frameworks

SOC2HIPAAPCI-DSSNIST

AWS documentation

Read the AWS guidance

Intentional? Suppress this finding

Sometimes a flag is deliberate โ€” a genuinely public endpoint, say. You can dismiss cloudfront-tls-outdated and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "cloudfront-tls-outdated", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::cloudfront-tls-outdated',
  reason: 'Why this is intentional',
});

Use the rule ID cloudfront-tls-outdated shown above โ€” not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs โ†’

Catch this in your stack

$ npx cdk-insights scan

CDK Insights runs this and 118+ other rules locally against your synthesised CDK app โ€” free, no account, your code never leaves your machine.

More CloudFront rules