From the source
Amazon's guide shows how to connect Amazon Bedrock AgentCore Gateway to private APIs and MCP servers when a central network team owns every VPC and a central firewall must inspect all traffic in both directions.
- The pattern keeps subnet ownership with the network team and routes Gateway traffic through the inspection VPC, using self-managed mode with one change: the network account owns the VPC Lattice resource gateway and places it in subnets routed through AWS Transit Gateway.
- The resource gateway gets its own VPC and subnets in the network account, which are not shared and kept free of backends, and one resource configuration per backend is shared with the AgentCore account through AWS RAM.
- The guide covers where to place the resource gateway, who owns each piece, six configuration decisions, and the checks that confirm the pattern works.
- Amazon says it built and tested the pattern in the US East (N. Virginia) Region in a lab with three member accounts and a management account in AWS Organizations, and the CloudFormation templates, test scripts, test evidence and reference material are in a companion repository.
- Amazon notes the pattern is a guideline to adjust to your own account architecture, and the post lists limits under what the pattern doesn't do.






