AWS details cross-organizational A2A multi-agent reference architecture
An AWS post walks through a deployed reference architecture in which a LangChain-based enterprise orchestrator communicates with a Strands Agents-based SaaS agent across separate AWS accounts using the Agent-to-Agent (A2A) protocol. Three agents run in the two accounts with OAuth authentication in both directions. Each account has its own Amazon Cognito user pool, allowing each side to authenticate through its own identity provider without sharing secrets. The system is deployed through three Jupyter notebooks and tested end to end.
AWS presents the architecture as a way for agents built by different organizations on different frameworks to collaborate across organizational trust boundaries without requiring either side to depend on the other’s framework or SDK.
Agents in multi-agent systems that span organizational boundaries often need to collaborate in a composable, interoperable way, with agents that other organizations build and run. They need a way to discover each other, communicate, and exchange tasks without exposing internals or requiring the same framework on both sides.
The Agent-to-Agent (A2A) protocol addresses this constraint. Without A2A, building composable multi-agent systems across organizational boundaries requires custom integration code for each customer and framework. Independent software vendors (ISVs) can instead build composable, interoperable agents that work with the A2A-compatible frameworks their customers already use.
While we frame this post around the ISV use case, the pattern also applies to organizations that expose agents across boundaries, whether to partners, customers, or internal teams that use different frameworks. As your system grows, you add skills by registering Agent Cards with the orchestrator, without changing the agents already running.
In this post, we walk through a deployed reference architecture on AWS. A LangChain-based enterprise orchestrator communicates with a Strands Agents-based software as a service (SaaS) agent across organizational boundaries using A2A, with the enterprise and the SaaS provider in separate AWS accounts. Neither side depends on the other’s framework or SDK, and the two sides share no secrets. We cover the architecture and implementation patterns, then deploy the system from three Jupyter notebooks and run an end-to-end test.
#AWS#Agent-to-Agent (A2A)#LangChain#Strands Agents#Amazon ECS#Amazon Bedrock AgentCore#Amazon Cognito#Claude Sonnet 4.6#OAuth 2.0#OpenID Connect