What changed
AWS has introduced a new pattern that enables Amazon Bedrock AgentCore Gateway to connect to private APIs and Model Context Protocol (MCP) servers in a hub-and-spoke network, while ensuring traffic passes through a central firewall for inspection. This pattern is designed for environments where a central network team owns all virtual private clouds (VPCs), subnets, and AWS Transit Gateway attachments, and where traffic between VPCs must be inspected in both directions.
What this means in practice
The solution involves placing a resource gateway in a VPC managed by the network team, which routes traffic through AWS Transit Gateway to ensure all requests and responses pass through the central inspection VPC. This setup allows the Gateway to access private APIs and MCP servers while meeting the security requirements of the network team. The resource gateway is configured using AWS Resource Access Manager (AWS RAM) to share resource configurations with the AgentCore account. The pattern was tested in the US East (N. Virginia) AWS Region with a lab environment consisting of three member accounts and a management account in AWS Organizations.
Limitations and availability
The pattern does not support payload inspection, as traffic is encrypted end-to-end between the Gateway and the backend, with only metadata and TLS Server Name Indication (SNI) visible to the firewall. Some traffic legs, such as agent-to-interface-endpoint and Gateway-to-resource-gateway, do not cross the firewall. Additionally, the pattern does not provide end-user identity at the tool level, as calls carry the Gateway’s client identity. The solution is available as a guideline and requires adjustment to fit specific account architectures.
