AWS Publishes A2A Cross-Organization Multi-Agent Reference Architecture
Start here
AWS published a reference architecture for cross-organization multi-agent systems built on the A2A protocol. In the design, an enterprise orchestrator built with LangChain and running on Amazon ECS calls a compliance SaaS agent built with Strands Agents and hosted on Amazon Bedrock AgentCore. The two sides sit in separate AWS accounts and share no secrets; each authenticates with tokens from its own Amazon Cognito user pool. The SaaS agent also calls back to an enterprise context agent for account metadata, so the agents act as peers rather than as client and server. The system deploys from three Jupyter notebooks that provision five CloudFormation stacks and run an end-to-end test plus seven trust boundary checks. AWS says the setup requires a Jupyter environment with Python 3.10 or later, incurs charges for the resources it creates, and should be deployed only in sandbox accounts with no customer or business data, with the stacks deleted after testing.
Generated from reports · updated 19 h ago
Report timeline
Follow the reports to see the event from different sides.
- AWS Machine Learning BlogAWS walks through building cross-organization multi-agent systems with A2A
AWS published a reference architecture in which a LangChain-based enterprise orchestrator on Amazon ECS calls a Strands Agents-based compliance SaaS agent on Amazon Bedrock AgentCore over the A2A protocol, with the two sides in separate AWS accounts and no shared secrets. Each side authenticates with tokens from its own Amazon Cognito user pool, and the SaaS agent calls back to an enterprise context agent for account metadata, so the agents act as peers rather than client and server. The system deploys from three Jupyter notebooks that provision five CloudFormation stacks and run an end-to-end test plus seven trust boundary checks.
Heat for this event
Not enough continuous observations yet to draw a trend.