S3 Bucket Encryption Not Customer-Configured

What this rule checks

Detects S3 buckets without an explicit BucketEncryption configuration (SSE-S3 default applies, not customer-controlled).

How to fix it

1. 1Set BucketEncryption explicitly — SSE-KMS with a customer-managed key where compliance requires auditable key control

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-encryption-aws-managed and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "s3-bucket-encryption-aws-managed", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

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

Use the rule ID s3-bucket-encryption-aws-managed 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