Check ID: bedrock_vpc_endpoints_configured
Provider: AWS
Service: bedrock
Severity: MEDIUM
Categories: internet-exposed, trust-boundaries, gen-ai
Resource type: AwsEc2VpcEndpointService

What this check verifies

Amazon VPCs are evaluated for interface VPC endpoints to all Bedrock services: bedrock, bedrock-runtime, bedrock-agent, bedrock-agent-runtime, and bedrock-mantle (OpenAI-compatible API). Only endpoints in available state are considered. Their presence indicates private Bedrock API connectivity over AWS PrivateLink within the VPC.

Risk

Without private Bedrock endpoints, control plane and runtime API traffic exits the VPC via IGW or NAT Gateway. This expands exposure to network path threats (e.g., DNS hijack, MITM), weakens egress isolation, and adds an internet dependency for Bedrock API access, reducing availability if NAT or edge paths fail.

Recommendation

Use interface VPC endpoints for all Bedrock services (bedrock, bedrock-runtime, bedrock-agent, bedrock-agent-runtime, bedrock-mantle) in each VPC that requires Bedrock API access.
  • Enable private DNS to keep calls on the AWS network
  • Apply restrictive endpoint policies (least privilege)
  • Reduce reliance on public egress and layer controls for defense in depth

Remediation

aws ec2 create-vpc-endpoint —vpc-id <VPC_ID> —service-name com.amazonaws.<REGION>.bedrock-runtime —vpc-endpoint-type Interface —subnet-ids <SUBNET_ID> && aws ec2 create-vpc-endpoint —vpc-id <VPC_ID> —service-name com.amazonaws.<REGION>.bedrock —vpc-endpoint-type Interface —subnet-ids <SUBNET_ID> && aws ec2 create-vpc-endpoint —vpc-id <VPC_ID> —service-name com.amazonaws.<REGION>.bedrock-agent —vpc-endpoint-type Interface —subnet-ids <SUBNET_ID> && aws ec2 create-vpc-endpoint —vpc-id <VPC_ID> —service-name com.amazonaws.<REGION>.bedrock-agent-runtime —vpc-endpoint-type Interface —subnet-ids <SUBNET_ID> && aws ec2 create-vpc-endpoint —vpc-id <VPC_ID> —service-name com.amazonaws.<REGION>.bedrock-mantle —vpc-endpoint-type Interface —subnet-ids <SUBNET_ID>

References

Where this check fires

This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable by Check ID = bedrock_vpc_endpoints_configured. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks