S3 Intelligent Tiering

What this rule checks

Recommends S3 Intelligent Tiering for cost optimization.

How to fix it

1. 1Enable S3 Intelligent-Tiering for buckets with varying access patterns
2. 2Configure archive access tiers for infrequently accessed data

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

new Bucket(this, 'DataBucket');

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

new Bucket(this, 'DataBucket', {
  intelligentTieringConfigurations: [{ name: 'archive-cold-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-intelligent-tiering and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "s3-intelligent-tiering", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

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

Use the rule ID s3-intelligent-tiering 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