Amazon Bedrock AgentCore Gateway Supports Private Connectivity Patterns

AWS has published technical guidance, across machine learning and networking blog posts and the Amazon Bedrock AgentCore documentation, on keeping traffic to AgentCore Gateway targets off the public internet for compliance and auditability. The guidance covers connecting resources via Amazon VPC Lattice, reaching REST API targets through private endpoints, using interface VPC endpoints (AWS PrivateLink), and attaching AWS targets through Elastic Network Interfaces.

The AgentCore documentation describes using interface VPC endpoints to create private connections between a VPC and AgentCore "without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection." It lists three PrivateLink endpoints: data plane com.amazonaws.region.bedrock-agentcore, control plane com.amazonaws.region.bedrock-agentcore-control, and gateway com.amazonaws.region.bedrock-agentcore.gateway. A compatibility table shows which primitives are supported over each endpoint, including a note that Evaluations are not yet supported on the data plane.

AWS describes two VPC Lattice modes for integrating MCP servers: a managed option where AgentCore provisions and manages Lattice resources, and a self-managed option that the customer controls for added governance and visibility. AWS deployment guides add companion design choices, such as whether to use a NAT gateway for outbound internet access or rely on VPC endpoints when only AWS service access is required.

Platform teams building agentic workloads commonly require private connectivity to reduce compliance scope and centralize auditing. The typical tradeoffs are ease of configuration (managed VPC Lattice), granular API-level control (PrivateLink), and full network-level attachment (ENIs) for low-latency or native VPC presence. Region availability of the PrivateLink endpoints and the evolving compatibility matrix are worth tracking before standardizing on a pattern.