Eon cuts engineer onboarding from 2 days to 2 minutes with an MCP Gateway on Bedrock AgentCore
AWS ML Blog · rss · 2026-10-20
An AWS ML Blog case study with backup company Eon describes consolidating dozens of investigation tools across AWS, GCP, and Azure behind a single MCP gateway on Amazon Bedrock AgentCore.
- Previously each tool needed its own credentials, developers ran local MCP servers, and cross-account access required per-account networking; new engineers took 2 days to onboard
- One AgentCore MCP Gateway now serves as the company-wide front door: humans authenticate via corporate SSO (Cognito JWTs), while the autonomous SRE agent (Claude on Bedrock) uses clientcredentials grants
- Cedar policies enforce least privilege — humans get read-only, only specific agent identities can write (e.g., PR comments), production tools stay read-only; policies are managed as code via GitHub PRs
- AgentCore Runtimes convert local stdio MCP servers into Streamable HTTP endpoints across multiple AWS accounts
Result: new engineers reach all investigation tools in about two minutes with identity separation between humans and agents.
More from coding & agent
- OpenAI's dots can now use company tools via Merge for Workforce with employee-bound permissions — shensi · 2026-10-21
- The topology of an LLM agent: where the model, loop, and tools run shapes cost and security — davidcrawshaw · 2026-10-21
- Agents with full-disk and accessibility access are an enterprise security nightmare, argues Runlayer — leveragedupside · 2026-10-21
- Acellera runs an unsupervised virtual lab of AI scientists on a real IL-23 molecular discovery program — gdefabritiis · 2026-10-21
- Pydantic author experiments with JS/TS and React support in the Monty sandbox — samuelcolvin · 2026-10-21
- Supabase lets coding agents query your logs to catch errors and slow queries — dshukertjr · 2026-10-21