# AWS introduces multi-account AI agent architecture with AgentCore Gateway and MCP

Digest AI · Enterprise & Industry · published 2026-09-24T16:12:47Z

Canonical: https://digestai.news/story/aws-introduces-multi-account-ai-agent-architecture-with-agentcore-gate

## Summary

AWS has detailed a new architecture for enterprises to build AI agents that query data across multiple AWS accounts without centralizing it. The solution uses **AgentCore Gateway** and **Model Context Protocol (MCP)** to let each line-of-business (LOB) team keep its data isolated while agents access only the required information at query time. The platform account hosts the agent and inference through **Amazon Bedrock**, while LOB teams expose their data and tools as MCP servers. AgentCore Gateway aggregates these servers into a single endpoint, enabling unified tool discovery, authentication via **AgentCore Identity**, and fine-grained authorization with **Policy in AgentCore**—all while keeping data within its original account boundaries.

The setup avoids replicating data or untangling cross-account IAM complexities. Each LOB’s MCP server runs on **AgentCore Runtime**, a serverless environment with session isolation and consumption-based pricing. The platform team controls models, applies guardrails, and tracks costs centrally, while LOB teams retain ownership of their tool surfaces. Security measures include OAuth 2.0 machine-to-machine (M2M) credentials, Okta integration, and **allowedWorkloadConfiguration** to restrict direct access. Observability tools like **AgentCore Evaluations** and **Amazon CloudWatch** monitor performance, and cost attribution tags help allocate expenses back to the originating LOB. The architecture scales by adding new LOB targets to the Gateway, with no changes required to the agent’s code.

## Key points

- AgentCore Gateway aggregates MCP servers from multiple AWS accounts into a single endpoint for unified tool discovery and invocation
- LOB teams expose data as MCP servers on AgentCore Runtime, keeping ownership and isolation while enabling agent access
- Security relies on OAuth 2.0 M2M credentials, Okta/OIDC validation, and Policy in AgentCore for fine-grained authorization

## Why it matters

This architecture lets enterprises scale AI agents across distributed data without copying or centralizing sensitive information, addressing a key pain point for multi-team organizations. It also centralizes governance, observability, and cost tracking while maintaining LOB autonomy over their data and tools.

## Sources

1. [Build a multi-account AI agent with AgentCore Gateway and MCP](https://aws.amazon.com/blogs/machine-learning/build-a-multi-account-ai-agent-with-agentcore-gateway-and-mcp) (AWS Machine Learning Blog, 2026-09-24, primary source)

## Cite

Digest AI, "AWS introduces multi-account AI agent architecture with AgentCore Gateway and MCP", 24 September 2026, https://digestai.news/story/aws-introduces-multi-account-ai-agent-architecture-with-agentcore-gate

---

Written by Digest AI's editorial model from the linked sources; the sources are the record. Headlines, digests and key points are written by Digest AI and may be quoted with a link to the story page. Linked articles belong to their publishers. Terms: https://digestai.news/terms#reuse
JSON: https://digestai.news/story/aws-introduces-multi-account-ai-agent-architecture-with-agentcore-gate.json