S3 Replication Missing

What this rule checks

Detects critical S3 buckets without cross-region replication.

How to fix it

1. 1Enable cross-region replication for disaster recovery
2. 2Configure replication rules for critical data

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

new Bucket(this, 'PrimaryStore', {
  bucketName: 'prod-app-data',
  versioned: true,
});

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

const replica = new Bucket(this, 'ReplicaStore', { versioned: true });
new Bucket(this, 'PrimaryStore', {
  bucketName: 'prod-app-data',
  versioned: true,
  replicationRules: [{ destination: replica }],
});

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

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