EKS Private Endpoint Access Disabled

What this rule checks

Detects EKS clusters with public API access but no private endpoint access.

How to fix it

1. 1Set ResourcesVpcConfig.EndpointPrivateAccess to true so node/API traffic stays inside the VPC

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 eks-private-endpoint-access-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "eks-private-endpoint-access-disabled", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::eks-private-endpoint-access-disabled',
  reason: 'Why this is intentional',
});

Use the rule ID eks-private-endpoint-access-disabled shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →

More EKS rules