# Amazon — Build composable, interoperable multi-agent systems with A2A on AWS

- Company: Amazon (amazon.com)
- Announced: 2026-11-12T15:42:21+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/build-composable-interoperable-multi-agent-systems-with-a2a-on-aws/
- Record: https://forck.live/items/35325-build-composable-interoperable-multi-agent-systems-with-a2a-on-aws
- Subject: Bedrock / Nova
- Models affected: Anthropic Claude Sonnet 4.6, Amazon Nova Lite

AWS published a reference architecture for connecting agents built on different frameworks across organizational boundaries using the Agent-to-Agent (A2A) protocol, with each side in its own AWS account. The walkthrough pairs a LangChain-based enterprise orchestrator with a Strands Agents-based compliance SaaS agent, and neither side depends on the other's framework or SDK. During onboarding the two parties exchange only public values such as identity provider URLs, client IDs, scopes and endpoint URLs, and each side then trusts tokens from the other's Amazon Cognito user pool, so no secrets are shared. The orchestrator fetches the SaaS agent's Agent Card at startup and creates a LangChain tool for each skill on it, so the model picks the tool and no hardcoded routing is needed. The enterprise orchestrator uses Anthropic Claude Sonnet 4.6 on Amazon Bedrock, while the internal context agent uses Amazon Nova Lite and the official a2a-sdk pinned to 1.2.2. The system deploys from three Jupyter notebooks and is tested end to end, with the enterprise agents running in private subnets without public IP addresses.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/build-composable-interoperable-multi-agent-systems-with-a2a-on-aws/:

> 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.

---

Record: https://forck.live/items/35325-build-composable-interoperable-multi-agent-systems-with-a2a-on-aws
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
