Amazon Bedrock AgentCore Memory adds cross-account access for multi-account agents
AWS continues hardening Bedrock AgentCore for production multi-account architectures. The new cross-account access for AgentCore Memory lets memory resources live in one AWS account while agents that consume that memory run in others. Resource-based policies grant principals in one account permission to call the memory data-plane APIs in another, and delivery destinations like S3 are configurable—mirroring the IAM patterns enterprises already use for cross-account data sharing.
The practical value is organizational: large enterprises typically separate environments (dev/prod, business units, security boundaries) into distinct AWS accounts. Without cross-account memory, agent memory couldn't be shared or centralized across those boundaries, forcing duplication or brittle workarounds. This makes AgentCore viable for the kind of federated, multi-team agent deployments that real enterprises need.
It's part of a steady stream of AgentCore expansion at the AWS Summit New York and after—web search, managed knowledge bases, policy guardrails, and multi-tenant pool-model patterns demonstrated through healthcare agents serving multiple clinics. AWS is methodically filling in the production plumbing (identity, memory, isolation, governance) rather than chasing model headlines.
Competitively, this is AWS's answer to agent platforms from Microsoft (Copilot/Foundry), Google (Vertex/ADK), and a wave of startups—differentiating on enterprise-grade infrastructure, security, and integration with the broader AWS account model rather than on a flagship model.
What to watch: AWS's Swami Sivasubramanian framed Amazon Q, AgentCore, and Continuum as 'eliminating every barrier between proof of concept and production.' The test is whether enterprises actually move agents from pilots to production at scale, where cross-account memory, multi-tenancy, and guardrails matter far more than demo polish. These unglamorous features are exactly what production adoption requires.
