S3 Bucket Versioning Disabled

What this rule checks

Detects S3 buckets without versioning enabled, leaving overwritten or deleted objects unrecoverable.

How to fix it

1. 1Set VersioningConfiguration.Status to Enabled on the bucket
2. 2Add lifecycle rules to expire noncurrent versions and control cost

import * as s3 from 'aws-cdk-lib/aws-s3';

new s3.Bucket(this, 'Bucket');

import * as s3 from 'aws-cdk-lib/aws-s3';

new s3.Bucket(this, 'Bucket', { versioned: 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 s3-bucket-versioning-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID s3-bucket-versioning-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