Skip to content
Hot eventWatching

AWS publishes hub-and-spoke pattern for AgentCore Gateway private APIs

1 reports1 reporting sourcesUpdated 1 d ago

Start here

AI digest

AWS published a hub-and-spoke network pattern and reference implementation for connecting Amazon Bedrock AgentCore Gateway to private APIs and MCP servers while keeping every VPC subnet owned by a central network team. All Gateway-to-backend traffic is routed through a central firewall in both directions, AWS says. The pattern uses self-managed mode with a VPC Lattice resource gateway placed in network-account subnets routed through AWS Transit Gateway, with one resource configuration per backend shared via AWS RAM. AWS says it built and tested the pattern in us-east-1 in a lab with three member accounts and a management account in AWS Organizations, using AWS Network Firewall and no source NAT; CloudFormation templates and validation scripts are in a companion repository. AWS advises treating the pattern as a guideline, adjusting it to your own account architecture, and running its checks in a non-production copy of your network account with your own firewall before relying on it.

Generated from reports · updated 23 h ago

Report timeline

Follow the reports to see the event from different sides.

November 19
  1. AWS Machine Learning Blog
    Connect Amazon Bedrock AgentCore Gateway to private APIs in a hub-and-spoke network with centralized inspection

    AWS shows how to connect Amazon Bedrock AgentCore Gateway to private APIs and MCP servers while keeping every VPC subnet owned by a central network team and routing all Gateway-to-backend traffic through a central firewall in both directions. The pattern uses self-managed mode with a VPC Lattice resource gateway placed in network-account subnets routed through AWS Transit Gateway, with one resource configuration per backend shared via AWS RAM. It was built and tested in us-east-1 across three member accounts plus a management account, with CloudFormation templates and validation scripts in a companion repository.

Heat for this event

Current, comparable range
5
Peak, comparable range
10November 19 05:00
Change in 24 hours
–

The trend compares the same participants over hours observed continuously, so its range can be narrower than the current heat count. Hover or tap the chart for hourly heat; the arrow keys move through it.