How Eon built multi-cloud investigation with an MCP Gateway on Amazon Bedrock AgentCore
Learn how Eon replaced per-tool credentials and local MCP processes across AWS, GCP, and Azure with a single authenticated Amazon Bedrock AgentCore gateway, giving more than 100 developers and autonomous agents unified access to production investigation and cutting new-engineer onboarding from two days to two minutes.
Eon, an independent software vendor specializing in AI-powered products, needed a solution to connect agents and humans to numerous operational tools across AWS, GCP, and Azure. The integration surface multiplied with each new tool added, leading to challenges in credential consolidation, eliminating local MCP processes, and providing identity separation.
Eon opted for Amazon Bedrock AgentCore Gateway, a managed gateway with built-in identity federation, Cedar-based authorization policies, and Runtime hosting. This solution addressed the company's requirements without the need for custom infrastructure. Eon deployed the full Amazon Bedrock AgentCore stack, including AgentCore Gateway, Policy, Runtime, and Identity, all capabilities of Amazon Bedrock AgentCore.
A single AgentCore MCP Gateway served as the company-wide front door, enforcing least-privilege access through Cedar policies. Developers and autonomous SRE agents used Claude on Amazon Bedrock and connected to the gateway with different identities. Cedar policies mapped each principal to permitted tools, with write operations limited to low-impact collaboration actions and production tools being read-only.
Written by urgent.news from AWS Machine Learning's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
