Home
Storia in 1 fonti
Mix and Match: One Agent, Three Clouds, One Protocol
The same research agent built three times — Google ADK on Cloud Run, Strands on Bedrock AgentCore, Agent Framework on Container Apps — all speaking A2A v1.0. Where the platforms differ, where the models differ, and what has to be held constant before either is readable.
Raccontata da
dev.to
Timeline cronologica
- ·
Mix and Match: Serving a Bedrock Agent to Google and Azure
A step by step guide to running a Strands agent on Amazon Bedrock AgentCore Runtime, serving the A2A protocol to callers on Google Cloud and Azure, with no AWS access key anywhere.
- ·
Mix and Match: Serving an ADK Agent to AWS and Azure
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…
- ·
Mix and Match: One Agent, Three Clouds, One Protocol
The same research agent built three times — Google ADK on Cloud Run, Strands on Bedrock AgentCore, Agent Framework on Container Apps — all speaking A2A v1.0. Where the platforms…
- ·
Multi-Everything Agent Infrastructure: How AWS Teams Avoid Lock-In While Running Dozens of Agentic Systems
Architectural patterns for operating many agent systems across heterogeneous frameworks, models, and providers without creating vendor dependencies.
- ·
What Bedrock AgentCore Actually Puts on Your A2A Agent Card
This article provides a step by step look at the A2A agent card a Strands agent publishes on Amazon...