RDS Credentials Without Secrets Manager Rotation

What this rule checks

Detects RDS databases that manage their own master credentials without Secrets Manager — no managed master password, no secretsmanager dynamic reference.

How to fix it

1. 1Use RDS-native managed credentials (manageMasterUserPassword) or a Secrets Manager secret referenced via {{resolve:secretsmanager:...}}

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

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "stack-rds-secret-rotation-missing", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::stack-rds-secret-rotation-missing',
  reason: 'Why this is intentional',
});

Use the rule ID stack-rds-secret-rotation-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 RDS rules