IAM Permission Boundary Missing

What this rule checks

Detects IAM roles without permission boundaries.

How to fix it

1. 1Create a permission boundary policy
2. 2Attach the permission boundary to IAM roles

import { Role, ServicePrincipal } from 'aws-cdk-lib/aws-iam';

new Role(this, 'PipelineDeployRole', {
  assumedBy: new ServicePrincipal('codepipeline.amazonaws.com'),
});

import { Role, ServicePrincipal, ManagedPolicy } from 'aws-cdk-lib/aws-iam';

new Role(this, 'PipelineDeployRole', {
  assumedBy: new ServicePrincipal('codepipeline.amazonaws.com'),
  permissionsBoundary: ManagedPolicy.fromAwsManagedPolicyName('PowerUserAccess'),
});

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

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "iam-permission-boundary-missing", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

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

Use the rule ID iam-permission-boundary-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 IAM rules