Connect Amazon Bedrock AgentCore Gateway to private APIs in a hub-and-spoke network with centralized inspection
Loading article
Security/Networking/Software Architecture
Connect Amazon Bedrock AgentCore Gateway to private APIs in a hub-and-spoke network with centralized inspection
AWS Machine Learning Blog·Today·19 min read
By Puneeth Komaragiri
Google CloudRAGSecurityMonitoringSoftware ArchitectureDockerAWS
AI summary
This article details a hub-and-spoke network architecture for Amazon Bedrock AgentCore that enforces centralized firewall inspection for all inter-VPC traffic. By placing the VPC Lattice resource gateway within a central network account and routing traffic through a transit gateway, organizations can maintain strict network control while allowing application teams to manage their own services and security groups.
Key points
Use a centralized network account to host VPC Lattice resource gateways to ensure all traffic passes through central firewalls.
Implement Amazon VPC Lattice in self-managed mode to allow centralized control of egress points while application teams manage backend resources.
Route traffic through an AWS Transit Gateway to maintain consistent inspection policies across multiple VPCs.
Use AWS Resource Access Manager to share application subnets between the network account and workload accounts.
Manage connection timeouts and quotas by configuring keepalives for MCP streams and splitting gateways by domain.