# Amazon — Connect Amazon Bedrock AgentCore Gateway to private APIs in a hub-and-spoke network with centralized inspection

- Company: Amazon (amazon.com)
- Announced: 2026-11-18T19:05:45+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/connect-amazon-bedrock-agentcore-gateway-to-private-apis-in-a-hub-and-spoke-network-with-centralized-inspection/
- Record: https://forck.live/items/38177-connect-amazon-bedrock-agentcore-gateway-to-private-apis-in-a-hub-and-spoke
- Subject: Bedrock / Nova

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.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/connect-amazon-bedrock-agentcore-gateway-to-private-apis-in-a-hub-and-spoke-network-with-centralized-inspection/:

> In many enterprises, a central network team owns every virtual private cloud (VPC) and subnet, and every flow between VPCs must pass a central firewall in both directions. Agents that call internal REST APIs and Model Context Protocol (MCP) servers through Amazon Bedrock AgentCore Gateway , a capability of Amazon Bedrock AgentCore, must meet the same two requirements. Amazon Bedrock AgentCore is a platform to build, connect, and optimize agents at scale, with any framework or model.
> 
> This post shows a pattern that meets both requirements. The network team keeps ownership of every subnet, and traffic between the Gateway and your private APIs and MCP servers crosses the central firewall in both directions. It covers where to place the Amazon VPC Lattice resource gateway that the Gateway uses to reach private targets. It also covers who owns each piece, six configuration decisions, and the checks that confirm the pattern works.
> 
> We built and tested the pattern in the US East (N. Virginia) AWS Region ( us-east-1 ), in a lab with three member accounts and a management account in AWS Organizations.

---

Record: https://forck.live/items/38177-connect-amazon-bedrock-agentcore-gateway-to-private-apis-in-a-hub-and-spoke
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
