Choosing the right network architecture for Amazon Bedrock AgentCore
Networking & Content Delivery Blog
This article compares two network architecture options for Amazon Bedrock AgentCore agents to access private resources in VPCs.
- AgentCore runtime with VPC support: agents connect directly through shared ENIs, best for small stable access patterns
- AgentCore Gateway with VPC Lattice: centralized policy layer with resource gateways, scales better as access patterns grow
- Direct access uses security groups for control; Gateway uses IAM SigV4 authentication at the policy layer
- Gateway supports cross-account access through AWS RAM sharing of resource configurations
- Direct access has lower latency and complexity initially; Gateway reduces security group sprawl at scale
- Both options can coexist in the same deployment rather than requiring migration
Choose direct access for stable, single-account deployments with few access patterns, or Gateway for growing, multi-account scenarios requiring centralized access control.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Oct 28
2026
2026
Building an Agentic AI Platform on Amazon Bedrock AgentCore
Nov 13
2026
2026
Architecture patterns for fast session startup on Amazon Bedrock AgentCore runtime
Nov 17
2026
2026
Reducing token costs and latency in Amazon Bedrock AgentCore JSON workloads
Nov 4
2026
2026
How U Mobile built agentic telco operations with Amazon Bedrock AgentCore
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.