Connect Amazon Bedrock AgentCore Gateway to private APIs in a hub-and-spoke network with centralized inspection
Many enterprises run a centralized network model: one account owns every VPC and a central firewall inspects all traffic. This post shows a tested pattern for connecting Amazon Bedrock AgentCore Gateway to private APIs and MCP servers in that model, with the VPC Lattice resource gateway in the network account so every hop crosses the firewall.
The Amazon Bedrock AgentCore Gateway can connect to private APIs and Model Context Protocol (MCP) servers in a hub-and-spoke network while being inspected by a central firewall. This is achieved by placing a VPC Lattice resource gateway in the network account, which is owned by the network team. The Gateway uses this gateway to reach private targets, with traffic crossing the central firewall in both directions.
The resource gateway is given its own VPC and subnets within the network account, with routes through a transit gateway ensuring every request and reply passes through the inspection VPC. Shared resource configurations for backends are sent from the Gateway account to the AgentCore account through AWS Resource Access Manager (AWS RAM).
Written by urgent.news from AWS Machine Learning's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.