Skip to main content
LOWBackupReliability

Backup Plan Misconfigured

backup-plan-misconfigured

What this rule checks

Detects Backup plan rules without cross-region copy or lifecycle configuration.

How to fix it

  1. 1Add CopyActions to replicate backups cross-region for DR
  2. 2Set DeleteAfterDays / MoveToColdStorageAfterDays to manage retention and cost
FlaggedThe backup rule has neither CopyActions (no cross-region copy for disaster recovery) nor a Lifecycle (no retention / cold-storage transition). CDK Insights flags AWS::Backup::BackupPlan rules missing cross-region copy or lifecycle configuration.
import { CfnBackupPlan } from 'aws-cdk-lib/aws-backup';

new CfnBackupPlan(this, 'BackupPlan', {
  backupPlan: {
    backupPlanName: 'daily-plan',
    backupPlanRule: [
      {
        ruleName: 'DailyBackups',
        targetBackupVault: 'Default',
        scheduleExpression: 'cron(0 5 * * ? *)',
      },
    ],
  },
});
FixedThe rule now defines a lifecycle (moveToColdStorageAfterDays + deleteAfterDays) and a cross-region copyActions entry to a DR vault. With both present the finding clears.
import { CfnBackupPlan } from 'aws-cdk-lib/aws-backup';

new CfnBackupPlan(this, 'BackupPlan', {
  backupPlan: {
    backupPlanName: 'daily-plan',
    backupPlanRule: [
      {
        ruleName: 'DailyBackups',
        targetBackupVault: 'Default',
        scheduleExpression: 'cron(0 5 * * ? *)',
        lifecycle: {
          moveToColdStorageAfterDays: 30,
          deleteAfterDays: 365,
        },
        copyActions: [
          {
            destinationBackupVaultArn:
              'arn:aws:backup:us-west-2:111122223333:backup-vault:DrVault',
            lifecycle: { deleteAfterDays: 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

AWS::Backup::BackupPlan

Compliance frameworks

SOC2HIPAANIST

AWS documentation

Read the AWS guidance

Intentional? Suppress this finding

Sometimes a flag is deliberate โ€” a genuinely public endpoint, say. You can dismiss backup-plan-misconfigured and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "backup-plan-misconfigured", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::backup-plan-misconfigured',
  reason: 'Why this is intentional',
});

Use the rule ID backup-plan-misconfigured shown above โ€” not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs โ†’

Catch this in your stack

$ npx cdk-insights scan

CDK Insights runs this and 118+ other rules locally against your synthesised CDK app โ€” free, no account, your code never leaves your machine.

More Backup rules