Home / Blog / Connect Amazon Bedrock AgentCore Gateway to private APIs
Tech News

Connect Amazon Bedrock AgentCore Gateway to private APIs

AWS detailed a tested pattern to link Bedrock AgentCore Gateway to private APIs via VPC Lattice with central firewall inspection across every inter-VPC hop.

By Dillip Chowdary • Nov 19, 2026 • Source: AWS Machine Learning Blog

Connect Amazon Bedrock AgentCore Gateway to private APIs
Image: AWS Machine Learning Blog

At a glance

Product
Amazon Bedrock AgentCore Gateway
Platform
Amazon Bedrock AgentCore
Tested region
us-east-1
Minimum CLI
AWS CLI 2.37.7
Minimum SDK
Boto3 1.43.106
Inspection scope
TLS metadata and SNI only

Amazon Web Services detailed an architecture pattern connecting Amazon Bedrock AgentCore Gateway to private APIs and Model Context Protocol servers in enterprise networks. According to AWS Machine Learning Blog's report, the reference design enables organizations with centralized topologies to retain subnet ownership while routing agent traffic through an inspection firewall in both directions. The pattern was validated in the US East (N. Virginia) AWS Region using three member accounts and a management account in AWS Organizations.

This technical guide details the placement of Amazon VPC Lattice resource gateways, bidirectional transit routing, visibility constraints, team responsibilities, and required prerequisites. The architecture is designed for enterprise infrastructure engineers and security teams managing centralized environments where network accounts own all subnets and central firewalls must inspect inter-VPC agent calls.

01Architecture options and endpoint operating modes

Enterprise environments configure private targets using either managed mode or self-managed mode when connecting Bedrock agents to internal tools. In managed mode, AgentCore provisions the VPC Lattice resource gateway inside the gateway account. In self-managed mode, engineers deploy the resource gateway directly and link it to targets using VPC Lattice resource configurations shared across accounts through AWS Resource Access Manager.

Environment constraintRecommended target mode
Gateway account can own subnets reaching toolsManaged mode
Traffic between Gateway and tools bypasses central inspectionStandard self-managed mode
Backend tools reside on public endpointsStandard Gateway target

Alternative setups that host resource gateways in tool subnets or central endpoint clusters fail because they bypass transit routing to the firewall. Similarly, exposing tools over internet-facing load balancers with AWS WAF introduces unnecessary perimeter exposure for purely internal workloads. The tested architecture adapts self-managed mode so the network account retains gateway ownership while preserving central inspection.

02Network account ownership and transit routing

The central network account retains complete ownership of every virtual private cloud, subnet, and transit gateway attachment across the enterprise. Application teams deploy resources exclusively into subnets shared through AWS Resource Access Manager, maintaining control only over their application workloads and security groups. To prevent architectural conflicts, network administrators provision a dedicated VPC and subnets specifically for the resource gateway.

Standard self-managed deployments position resource gateways inside subnets with direct access to backend endpoints, which eliminates intermediate firewall inspection. Under the modified pattern, the network account routes resource gateway subnets through AWS Transit Gateway with appliance mode enabled. This topology ensures that all inbound requests and outbound responses cross the central firewall located in the inspection VPC.

03Six hops across the central firewall

Agent invocations follow a deterministic path across multiple account boundaries before reaching internal tool targets. Inside the agent VPC, client software initiates requests to the Gateway address using Amazon Route 53 private DNS resolution. The service evaluates access rules and inbound tokens before routing traffic to private network interfaces:

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

  1. Agent invocation Agents in shared subnets call the Gateway URL resolved via interface endpoints.
  2. Policy evaluation The Gateway evaluates AWS WAF rules, verifies inbound tokens, and selects the target.
  3. Lattice delivery The Gateway acquires outbound OAuth tokens and delivers traffic to the resource gateway.
  4. Firewall inspection The resource gateway subnets route across the transit gateway through the inspection VPC.
  5. Target execution The internal load balancer validates the token and forwards requests to backends.
  6. Return transit Response traffic returns through the transit gateway and inspection firewall to the agent.

Traffic reaches the network account without requiring a dedicated transit gateway attachment in the AgentCore account. When administrators create a target, AgentCore associates the shared resource configuration with its VPC Lattice service network. VPC Lattice manages the underlying transport to deliver connections directly to the resource gateway network interfaces in customer VPCs.

04Inspection boundaries and token credential limits

Security teams must account for clear inspection boundaries when deploying this architecture in corporate environments. Because connections maintain end-to-end TLS encryption from the Gateway to the internal Application Load Balancer, central firewalls inspect only flow metadata and TLS Server Name Indication headers. Firewall appliances cannot inspect application payloads, leaving body logging to Gateway, AWS WAF, and load balancer audit trails.

Several network segments also bypass the central inspection appliance by design. Traffic traveling between the agent and its interface endpoint, as well as connections moving from the Gateway into the resource gateway, does not cross the firewall. Similarly, outbound token requests executed by AgentCore directly to identity providers operate outside the transit gateway inspection path.

Note: Under client credentials authorization, every invocation reaching internal tools presents the client identity of the Gateway rather than individual callers. To associate specific requests with individual end users, engineers must correlate downstream load balancer timestamps against inbound token claims recorded in Gateway application logs.

05Cross account responsibilities and tool requirements

Operating this architecture requires structured divisions of responsibility among network administrators, application developers, and AgentCore operators. Clear administrative boundaries prevent deployment bottlenecks while ensuring uniform policy enforcement across organizational cloud accounts. The governance framework categorizes implementation tasks into initial infrastructure setup, recurring load balancer attachments, and routine tool registrations.

Responsibility scopeNetwork team tasksTool team tasksAgentCore team tasks
One-time setupDeploy resource gateway, VPC, routes, firewall rules, and RAM shareCreate ALB certificate matching target host nameDeploy Gateway, authorizer, resource policy, and optional WAF
Connected ALB API additionNoneAdd ALB listener rule with JWT validationCreate one Gateway target per API or MCP server
New ALB or tool accountAdd resource configuration to share and update firewall rulesProvision internal ALB, security groups, and OAuth clientConfigure target and register OAuth credential provider

Organizations must satisfy specific environment requirements before deploying this pattern across member accounts. Implementation requires an AWS Organizations deployment with resource sharing enabled in AWS RAM, transit gateways with appliance mode, and appropriate VPC Lattice IAM permissions. Client automation requires AWS CLI 2.37.7 or later, or AWS SDK for Python (Boto3) 1.43.106 or later.

Modifying operations on an existing target does not require provisioning replacement gateway resources. Engineers update OpenAPI definitions using the UpdateGatewayTarget action or synchronize Model Context Protocol servers with SynchronizeGatewayTargets. These declarative updates allow application teams to add capabilities without altering underlying network routing or central firewall rules.

Frequently asked questions

Can the central firewall inspect request payloads between AgentCore Gateway and private APIs?

No, traffic is encrypted with end-to-end TLS from the Gateway to the internal Application Load Balancer. The central firewall inspects network flow metadata and TLS Server Name Indication, while request payloads remain in application and Gateway logs.

Which AWS CLI and SDK versions are required for this pattern?

The architecture requires AWS CLI version 2.37.7 or later, or the AWS SDK for Python (Boto3) version 1.43.106 or later. These versions provide support for the certificateConfigurations parameter used during target setup.

How do updates to an existing API or MCP server propagate to AgentCore Gateway?

Teams do not need to create a new target when updating existing operations or tools. Developers can update the OpenAPI specification with UpdateGatewayTarget or call SynchronizeGatewayTargets for Model Context Protocol servers.

How does Gateway traffic enter the network account without a transit gateway attachment?

When a target is created, AgentCore associates the shared resource configuration with its VPC Lattice service network. VPC Lattice delivers connections across an AWS-operated hop directly to the resource gateway network interfaces in the network account.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →