A durable multi-account agent checklist that keeps data with its owning team
AWS published a multi-account AI-agent architecture on September 24. A central platform account runs the agent and model, while line-of-business accounts keep their data and expose only approved tools through MCP servers. AgentCore Gateway provides one endpoint for tool discovery, authentication, fine-grained authorization, and observability. This should become a durable governance task rather than a one-time deployment. Whenever an account, tool, model, or identity provider changes, recheck machine identity, user authorization, returned fields, tenant isolation, rate limits, cost ownership, and log completeness, then drill privilege escalation, expired credentials, tool-contract changes, and cross-account failures. Teams should reproduce the vendor's result with their own data, controls, workload, and operating limits before production adoption.
