Eon Centralizes Multi-Cloud Investigation Tools

Eon says its engineering team replaced per-tool credentials and local Model Context Protocol (MCP) processes with one authenticated Amazon Bedrock AgentCore Gateway to investigate incidents across AWS, GCP and Azure. In a guest post co-written with Eon’s Roei Zavida, AWS describes a production setup serving 100+ developers and an autonomous site reliability engineering (SRE) agent. Eon reports that onboarding now takes about two minutes, down from two days, and that developers use 0 local MCP processes, down from 10.

The company’s engineers investigate incidents across multiple clouds and operational systems. A crashed Kubernetes pod, for example, can require checking container logs, Grafana metrics, a GitHub pull request and cloud-provider health in one session. Eon sought to consolidate credentials, remove locally run MCP servers, separate human and agent permissions, and connect AWS accounts without VPC peering or per-account AWS PrivateLink. Its Claude-based SRE agent also needed access to investigation tools under different permissions from those granted to humans.

Eon considered a custom reverse proxy with custom authentication and Amazon Bedrock AgentCore Gateway. The proxy would have required Eon to build and maintain protocol translation, session management and authorization. Eon chose AgentCore Gateway, which AWS describes as providing managed identity federation, Cedar-based authorization and Runtime hosting that converts local MCP servers into remote HTTP endpoints. The deployment uses AgentCore Gateway, Policy, Runtime and Identity. Developers connect through one MCP URL; the agent uses the same gateway with a separate identity.

Corporate single sign-on federates through Amazon Cognito, which issues JSON Web Tokens for human users, while agents authenticate with client credentials. Cedar policies determine which principals can call which tools: approved human groups receive read access, production tools are read-only, and write actions are limited to specified identities and low-impact tasks such as commenting on a pull request or ticket. Production access is read-only, granted just in time through approval and audited. Policy changes are managed through reviewed GitHub pull requests.

AgentCore Gateway reaches Runtimes in other AWS accounts by assuming cross-account IAM roles. Eon says this removed VPC peering, route-table management, PrivateLink endpoint costs and security-group coordination; a new account’s setup changed from days to one IAM trust policy deployable in minutes. Most targets use Runtime with IAM. Eon wraps remote MCP servers when it needs to filter available tools or translate credentials.

During an investigation, the gateway combines tool listings from dozens of targets into one response containing hundreds of tools. A developer can ask for a payments service’s error-rate spike in the last hour; the IDE’s agent selects a Grafana query, the gateway checks the request against Cedar, and a Runtime runs it using a service credential held in the AgentCore Identity vault. The agent can then check Kubernetes status and the related GitHub pull request through other Runtimes.

Deployment to 100+ developers and about 10,000 sessions exposed policy-size and client-compatibility issues. Because pre-indexed tool schemas count toward Cedar policy size, Eon uses DYNAMIC listing for targets with large tool catalogs; the gateway fetches their tool lists on request, adding zero bytes to the policy. Semantic tool search is unavailable for those targets. Eon keeps DEFAULT mode for smaller targets that need per-user OAuth and pre-indexed schemas for consent. Claude Code, Cursor and Codex expect an OAuth state parameter for cross-site request forgery protection, while AgentCore uses session-URI binding. Eon built an Amazon API Gateway shim to translate between them. It also built a Runtime wrapper to filter large tool lists for individual developers.

Eon reports 0 credential sets per developer beyond one SSO login, compared with separate credentials for each system before; cross-account networking configurations fell from VPC peering per account to 0 through IAM. The gateway has processed about 10,000 sessions, and hundreds of tools are available from one URL across dozens of targets. Eon says its internal agent accounts for most of the time saved because it can access more context through the gateway, improving investigation accuracy. The company is exploring whether

Eon says its engineering team replaced per-tool credentials and local Model Context Protocol (MCP) processes with one authenticated Amazon Bedrock AgentCore Gateway to investigate incidents across AWS, GCP and Azure. In a guest post co-written with Eon’s Roei Zavida, AWS describes a production setup serving 100+ developers and an autonomous site reliability engineering (SRE) agent. Eon reports that onboarding now takes about two minutes, down from two days, and that developers use 0 local MCP processes, down from 10.

The company’s engineers investigate incidents across multiple clouds and operational systems. A crashed Kubernetes pod, for example, can require checking container logs, Grafana metrics, a GitHub pull request and cloud-provider health in one session. Eon sought to consolidate credentials, remove locally run MCP servers, separate human and agent permissions, and connect AWS accounts without VPC peering or per-account AWS PrivateLink. Its Claude-based SRE agent also needed access to investigation tools under different permissions from those granted to humans.

Eon considered a custom reverse proxy with custom authentication and Amazon Bedrock AgentCore Gateway. The proxy would have required Eon to build and maintain protocol translation, session management and authorization. Eon chose AgentCore Gateway, which AWS describes as providing managed identity federation, Cedar-based authorization and Runtime hosting that converts local MCP servers into remote HTTP endpoints. The deployment uses AgentCore Gateway, Policy, Runtime and Identity. Developers connect through one MCP URL; the agent uses the same gateway with a separate identity.

Corporate single sign-on federates through Amazon Cognito, which issues JSON Web Tokens for human users, while agents authenticate with client credentials. Cedar policies determine which principals can call which tools: approved human groups receive read access, production tools are read-only, and write actions are limited to specified identities and low-impact tasks such as commenting on a pull request or ticket. Production access is read-only, granted just in time through approval and audited. Policy changes are managed through reviewed GitHub pull requests.

AgentCore Gateway reaches Runtimes in other AWS accounts by assuming cross-account IAM roles. Eon says this removed VPC peering, route-table management, PrivateLink endpoint costs and security-group coordination; a new account’s setup changed from days to one IAM trust policy deployable in minutes. Most targets use Runtime with IAM. Eon wraps remote MCP servers when it needs to filter available tools or translate credentials.

During an investigation, the gateway combines tool listings from dozens of targets into one response containing hundreds of tools. A developer can ask for a payments service’s error-rate spike in the last hour; the IDE’s agent selects a Grafana query, the gateway checks the request against Cedar, and a Runtime runs it using a service credential held in the AgentCore Identity vault. The agent can then check Kubernetes status and the related GitHub pull request through other Runtimes.

Deployment to 100+ developers and about 10,000 sessions exposed policy-size and client-compatibility issues. Because pre-indexed tool schemas count toward Cedar policy size, Eon uses DYNAMIC listing for targets with large tool catalogs; the gateway fetches their tool lists on request, adding zero bytes to the policy. Semantic tool search is unavailable for those targets. Eon keeps DEFAULT mode for smaller targets that need per-user OAuth and pre-indexed schemas for consent. Claude Code, Cursor and Codex expect an OAuth state parameter for cross-site request forgery protection, while AgentCore uses session-URI binding. Eon built an Amazon API Gateway shim to translate between them. It also built a Runtime wrapper to filter large tool lists for individual developers.

Eon reports 0 credential sets per developer beyond one SSO login, compared with separate credentials for each system before; cross-account networking configurations fell from VPC peering per account to 0 through IAM. The gateway has processed about 10,000 sessions, and hundreds of tools are available from one URL across dozens of targets. Eon says its internal agent accounts for most of the time saved because it can access more context through the gateway, improving investigation accuracy. The company is exploring whether