S3 Lifecycle Policy Missing

What this rule checks

Detects S3 buckets without lifecycle policies.

How to fix it

1. 1Create lifecycle rules to transition objects to cheaper storage classes
2. 2Set expiration rules for temporary data
3. 3Use lifecycle rules to delete incomplete multipart uploads

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

new Bucket(this, 'DataBucket');

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

new Bucket(this, 'DataBucket', {
  lifecycleRules: [{
    transitions: [{ storageClass: StorageClass.GLACIER, transitionAfter: Duration.days(90) }],
    expiration: Duration.days(365),
  }],
});

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-lifecycle-policy-missing and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "s3-lifecycle-policy-missing", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::s3-lifecycle-policy-missing',
  reason: 'Why this is intentional',
});

Use the rule ID s3-lifecycle-policy-missing 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