AWS explains connecting LangChain and Strands agents across AWS accounts over A2A
Overview
AWS Machine Learning Blog shows how an enterprise orchestrator built with LangChain can call a SaaS compliance agent built with Strands Agents over the A2A protocol.
The two sides run in separate AWS accounts, each authenticates with its own Amazon Cognito user pool, and they share no secrets.
The post includes three Jupyter notebooks for deployment and an end-to-end test. It says the solution must be deployed in two AWS accounts in the same Region (us-east-1, us-east-2, or us-west-2), and that running it incurs charges for the resources it creates, plus usage charges for Amazon Bedrock and Amazon Bedrock AgentCore. AWS advises deploying only in sandbox accounts with no customer or business data, and deleting the stacks after testing.
Written by AI from the articles below · updated Nov 12, 11:44 AM ET
Check the sources:
Article timeline
The articles in this story. Times are ET.
- AWS Machine Learning BlogOfficialPickAWS shows how to connect multi-agent systems across organizations with A2A
AIAWS explains how a LangChain enterprise orchestrator can call a Strands Agents-based SaaS compliance agent over the A2A protocol across separate AWS accounts. Each side authenticates with its own Amazon Cognito user pool, and the two sides share no secrets. The post includes three Jupyter notebooks for deployment and an end-to-end test.
Heat Trend
- Current comparable heat
- 4
- Peak comparable heat
- 10Nov 12, 12:00 PM ET
- Change in past 24 hours
- -50%
The trend compares only continuously observed participants, so its scope may be smaller than the current heat total. Hover or tap for hourly heat; use arrow keys with a keyboard.