Skip to content
Agents tracked: 467 Releases (7d): 716 Agent status: all upSince last limit reset: Claude 37d · Codex 1d Updated Oct 29, 2026
Case study Eon

How Eon unified multi-cloud incident tooling behind one MCP Gateway on AgentCore

Eon, a cloud data protection vendor, replaced per-tool credentials and local MCP servers with a single authenticated MCP gateway on Amazon Bedrock AgentCore. Developers and an autonomous SRE agent now investigate production incidents across AWS, GCP and Azure through one URL with policy-based access.

The problem

Eon's engineers investigate production incidents across several clouds and dozens of operational systems, so one issue can involve logs, metrics, pull requests and cloud health checks. Each tool needed its own credentials, and each developer ran several local MCP servers. New engineers spent about two days on setup, and the SRE agent needed the same tools as humans but with narrower permissions.

How they did it

  1. Deploy AgentCore Gateway as one company-wide MCP endpoint, with Policy, Runtime and Identity alongside it.
  2. Federate corporate SSO through Amazon Cognito to issue JWTs for humans, and use client_credentials grants for agents.
  3. Host MCP servers on AgentCore Runtimes across several AWS accounts, converting local stdio servers into Streamable HTTP endpoints, and let the gateway reach them through IAM cross-account role assumption.
  4. Write Cedar policies in ENFORCE mode mapping SSO groups and agent identities to permitted tools, kept as code and reviewed through GitHub PRs.
  5. Use DYNAMIC listing mode for large tool catalogs to keep policy size down, and wrap some remote MCP servers in a Runtime that filters their tool lists.
  6. Add an Amazon API Gateway shim so Claude Code, Cursor and Codex can complete the OAuth flow.

Results

  • As reported by AWS (guest post co-written with Eon): developer onboarding dropped from 2 days to 2 minutes.
  • As reported by AWS: local MCP processes per machine went from 10 to 0, and per-system credential sets were replaced by one SSO login.
  • As reported by AWS: the setup serves 100+ developers and about 10,000 sessions, with hundreds of tools across dozens of targets behind one URL.
  • VPC peering between accounts was replaced by IAM trust policies, and one Cedar policy set now governs both humans and agents.

As reported by the source (AWS Machine Learning Blog (guest post)); AgentGid did not measure these figures.

Takeaway. A single MCP gateway with policy-as-code access control can give both developers and agents the same tools under different permissions, without per-tool tokens or local servers.
AgentGid's take

This suits platform or SRE teams already running on AWS, comfortable with Cognito/SSO federation, IAM cross-account roles and Cedar policy writing. Treat the 2-day-to-2-minute onboarding figure as AWS-reported, and expect the policy and OAuth shim work up front. If you only need the coding client side, OpenCode (Free + $10/mo, open source) is a cheaper alternative to Claude Code ($20/mo).

The agents used here

Compare: Claude Code vs Cursor · Claude Code vs OpenAI Codex · Cursor vs OpenAI Codex

Similar use cases

Guides