Connect Amazon Bedrock AgentCore Gateway to private APIs in a hub-and-spoke network with centralized inspection
Machine Learning Blog
This article describes a hub-and-spoke network pattern for connecting Amazon Bedrock AgentCore Gateway to private APIs and MCP servers with centralized firewall inspection using VPC Lattice resource gateways.
- Place the VPC Lattice resource gateway in a dedicated network account VPC routed through AWS Transit Gateway to ensure all traffic crosses the central firewall
- Share one resource configuration per backend load balancer with the AgentCore account through AWS RAM
- Validate tokens on internal ALBs or private APIs using JWT validation to authenticate Gateway requests
- Create Gateway targets referencing shared resource configurations with OAuth credential providers for tool account authentication
- Restrict Gateway access to private endpoints only using resource policies and endpoint policies
- Run validation checks to confirm requests originate from resource gateway, cross the firewall bidirectionally, and public endpoints are closed
This pattern enables enterprises with centralized network ownership and mandatory firewall inspection to securely connect Bedrock agents to private tools while maintaining network team control and application team autonomy.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.