← Back
AWS ML Blog

Build a multi-account AI agent with AgentCore Gateway and MCP

•19 min read•
#mcp#bedrock#amazon
✦TL;DR

The article demonstrates how to architect a multi‑account AI agent system that keeps each team’s data isolated in separate AWS accounts while enabling a unified query interface. It leverages Amazon Bedrock’s AgentCore Gateway as a central orchestrator, with each line‑of‑business account exposing its data via an MCP server that the gateway can route to. The design eliminates cross‑account data sharing while preserving a single agent experience, though it introduces cross‑account IAM complexity and potential latency from inter‑account calls. The approach is particularly useful for regulated environments that require strict data isolation.

⚡ Key Takeaways

  • The central platform account hosts an AgentCore Gateway that dispatches queries to MCP servers in other AWS accounts.
  • Each line‑of‑business account runs an MCP server that exposes its data as a Bedrock-compatible endpoint.
  • Cross‑account IAM roles must be configured so the gateway can assume the

Want the full story? Read the original article.

Read on AWS ML Blog ↗

More like this

Introducing workload recovery and expanded infrastructure checks on Amazon SageMaker HyperPod

AWS ML Blog•#deployment

How Airbnb uses cost per task to operate coding agents on Amazon Bedrock

AWS ML Blog•#amazon

Private certificate authority support in Amazon Bedrock AgentCore Identity

AWS ML Blog•#agents

How to Design MCP Servers That Leave Orchestration to the Host

Towards Data Science•#mcp

EXPLORE AI NEWS

Daily hand-picked stories on LLMs, RAG, agents and production AI — curated for engineers who ship.

BROWSE NEWS

GET THE WEEKLY DIGEST

Join engineers getting the Monday signal-over-noise AI breakdown. No spam, unsubscribe anytime.

LEARN AI ENGINEERING

Curated courses, research papers, repos and tutorials built for engineers leveling up in AI.

START LEARNING