AWS详解跨组织A2A多智能体参考架构
AWS在一篇文章中介绍了一套已部署的参考架构:基于LangChain的企业编排器通过智能体对智能体(A2A)协议,与部署在另一个AWS账户中的Strands Agents SaaS智能体通信。三个智能体分布在两个账户中,并采用双向OAuth认证。两个账户各有一个Amazon Cognito用户池,因此双方均可使用各自的身份提供商进行认证,且不共享密钥。系统通过三个Jupyter笔记本完成部署并进行端到端测试。
AWS表示,该架构让不同组织基于不同框架构建的智能体能够跨越组织信任边界协作,而任何一方都不需要依赖对方的框架或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