What is this project trying to do? Three AI agents, each built with a different vendor's...
A multi-cloud agent coordinator on Cloud Run orchestrates calls to three agents (GCP, AWS, Azure) using federated OIDC tokens, eliminating long-lived credentials from production. The choice of coordinator runtime determines the entire auth topology—a critical architectural decision for enterprises managing agents across multiple clouds without static secrets.
What is this project trying to do?
Three AI agents, each built with a different vendor's framework, each running on
that vendor's own hosting, all answering the same question at the same time:
Google — an ADK agent on Cloud Run
AWS — a Strands agent on Bedrock AgentCore Runtime
All three hyperscalers now ship an agent framework, and all three speak A2A. The protocol page will...
Every directed edge between Bedrock AgentCore, Microsoft Foundry, and Google ADK, deployed and measured over A2A v1.0 — the…
A Strands agent on Bedrock AgentCore Runtime serving A2A to callers on Google Cloud and Azure. The AgentCore container contract,…
Full disclosure up front: I run one of the four platforms in this test (redu.cloud), so take my...
This installment puts Microsoft Foundry in charge. Azure is the main cloud: it hosts the master...
This is the third in a series of posts documenting the architecture, implementation, and lessons...
