S3 Bucket Access Logging Disabled

What this rule checks

Detects S3 buckets without server access logging configured. Required by CIS AWS Foundations 2.1.2 and useful for incident forensics.

How to fix it

1. 1Set LoggingConfiguration.DestinationBucketName on the bucket to capture access logs
2. 2Use a separate bucket for logs to avoid recursive logging
3. 3Configure a lifecycle rule on the log bucket to manage storage costs

import { Bucket } from 'aws-cdk-lib/aws-s3';

new Bucket(this, 'DataBucket');

import { Bucket } from 'aws-cdk-lib/aws-s3';

const logBucket = Bucket.fromBucketName(this, 'CentralLogs', 'org-s3-access-logs');
new Bucket(this, 'DataBucket', {
  serverAccessLogsBucket: logBucket,
  serverAccessLogsPrefix: 'data/',
});

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 s3-bucket-access-logging-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID s3-bucket-access-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 S3 rules