VPC with private subnets has no KMS endpoint
- Severity
- Low
- Service
- KMS
- Check ID
- KMS_NO_VPC_ENDPOINT
What this check finds
KMS is in use but a VPC with private subnets calls the KMS API over the public internet rather than a private interface endpoint. An interface endpoint keeps key operations on the AWS network and lets an endpoint policy constrain access.
Passing looks like: Private KMS access via VPC endpoint.
How to fix it
Create an interface VPC endpoint for KMS.
AWS console
VPC → Endpoints → Create endpoint → com.amazonaws.{region}.kms (Interface) → select the VPC and private subnets → attach a restrictive security group.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs