AWS has published a reference architecture for agents that need information held by several business units without copying all of that data into one account. Each team exposes approved operations through a Model Context Protocol server, while Amazon Bedrock AgentCore Gateway presents those tools to the agent through a single endpoint.
The central platform account hosts the agent and model inference. Business-unit accounts keep their databases, S3 files and knowledge bases, returning only the result needed for a particular request. Gateway discovers tools, routes calls and applies authorization policies outside the agent’s code. The sample uses Okta and AgentCore Identity for OAuth machine-to-machine credentials.
A banking example exposes account-profile and balance lookups from one team and credit-score or lending-policy searches from another. User claims can be evaluated against Cedar policies before a call proceeds. Each remote server validates the inbound token, and production deployments can restrict access so calls must arrive through the approved gateway.
The design reduces data duplication but is not a turnkey connection. Organizations need a multi-account AWS setup, model access, an OpenID Connect identity provider and MCP servers for each participating team. AWS supplies a repository and deployment script using its Cloud Development Kit, plus a sample web application that shows which units were queried and which requests policy denied.