A Google ADK agent on Cloud Run, serving A2A to clients that are not ADK — a Strands agent on Bedrock AgentCore and an Agent Framework agent on Container Apps. The card that advertises your bind address, the reply that arrives twice, the event stream once a tool exists, and what Cloud Run brings to the mesh.
This article provides a step by step look at running a Google ADK agent on Cloud Run, and serving it over the A2A protocol to callers that are not ADK.
The code is here:
github.com/xbill9/multicloud-a2a-subagent
What is this project trying to Do?
This project aims to answer one research brief with three agents on three clouds, over one protocol, with no stored credentials between them.
A step by step guide to running a Strands agent on Amazon Bedrock AgentCore Runtime, serving the A2A protocol to callers on…
The same research agent built three times — Google ADK on Cloud Run, Strands on Bedrock AgentCore, Agent Framework on Container…
One ADK agent on Cloud Run, serving A2A to clients built on Strands and Microsoft Agent Framework, next to two agents that are…
This article provides a step-by-step guide to building and testing a cross-cloud currency agent. A...
This article provides a step-by-step guide to building and testing a cross-cloud currency agent. A...
This article explains how to build and test a cross-cloud currency agent. An Amazon Bedrock master...
