Security Group Has No Rules

What this rule checks

Detects security groups with no ingress or egress rules defined.

How to fix it

1. 1Add the intended rules, or delete the group if it is orphaned

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 security-group-no-rules and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "security-group-no-rules", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::security-group-no-rules',
  reason: 'Why this is intentional',
});

Use the rule ID security-group-no-rules shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →

More EC2 rules