Amazon Bedrock AgentCore Gateway: Now Supports Connecting to Private APIs in Centralized Hub-and-Spoke AWS Networks
Amazon has released a tested network pattern for connecting Bedrock AgentCore Gateway to private APIs in hub-and-spoke AWS network topologies with centralized traffic inspection using VPC Lattice resource gateways. This update is useful for enterprises with strict network controls.
What changed?
Amazon Bedrock AgentCore Gateway can now be connected to private APIs and Model Context Protocol (MCP) servers inside a hub-and-spoke AWS network that uses centralized firewall inspection. The supported approach places the Amazon VPC Lattice resource gateway in a dedicated VPC owned by the central network account. All inter-VPC traffic for API calls crosses a central firewall for inspection. Amazon has provided a tested and documented architectural pattern for this use case.

Why does it matter to an everyday developer?
Enterprises commonly enforce strict network controls and must inspect all inter-VPC traffic with a central firewall. Previously, connecting Amazon Bedrock AgentCore Gateway to private backends in such environments was not straightforward and could violate security policies or require custom solutions. This official pattern provides a compliant, scalable, and tested approach for accessing internal APIs through Bedrock AgentCore Gateway, allowing developers to leverage generative AI agents within existing secured cloud environments.
