AWS发布AgentCore私有API集中检查架构
AWS Machine Learning Blog发布了一套经过测试的架构模式,通过中心辐射网络连接 Amazon Bedrock AgentCore Gateway、私有API和MCP服务器,并实施集中式防火墙检查。该方案将Amazon VPC Lattice资源网关部署在网络账户中,同时提供六项配置决策、验证检查、CloudFormation模板、测试脚本、排障指导、配额和地址规划。AWS在us-east-1使用三个成员账户和一个AWS Organizations管理账户完成测试,并建议根据实际账户架构进行调整。
这套方案为企业团队提供了可执行的实施路径,可在连接智能体工作负载与内部API的同时,保留集中式网络管理和双向防火墙检查。
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. The AWS CloudFormation templates, test scripts, test evidence, and reference material (address plan, full validation checks, troubleshooting, quotas) are in the companion repository. Use the pattern as a guideline and adjust it to your own account architecture.
#AWS#Amazon Bedrock AgentCore#Amazon Bedrock AgentCore Gateway#Amazon VPC Lattice#AWS Network Firewall#AWS Organizations#AWS Resource Access Manager#AWS WAF#AWS CloudFormation#Model Context Protocol