CloudFront Logging Disabled

What this rule checks

Detects CloudFront distributions without access logging.

How to fix it

1. 1Enable standard logging to S3
2. 2Consider real-time logs for detailed analysis

import * as cloudfront from 'aws-cdk-lib/aws-cloudfront';
import * as origins from 'aws-cdk-lib/aws-cloudfront-origins';

new cloudfront.Distribution(this, 'Dist', {
  defaultBehavior: { origin: new origins.HttpOrigin('origin.example.com') },
});

import * as cloudfront from 'aws-cdk-lib/aws-cloudfront';
import * as origins from 'aws-cdk-lib/aws-cloudfront-origins';

new cloudfront.Distribution(this, 'Dist', {
  defaultBehavior: { origin: new origins.HttpOrigin('origin.example.com') },
  enableLogging: true,
});

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

Intentional? Suppress this finding

Sometimes a flag is deliberate — a genuinely public endpoint, say. You can dismiss cloudfront-logging-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID cloudfront-logging-disabled shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →

More CloudFront rules