Multi-Tenant Isolation: One Platform, Many Customers, Zero Bleed

Running one agent platform for many customers means every shared surface — context, memory, credentials, caches, traces, quotas — is a potential cross-tenant leak. The four bleed paths, the isolation boundary at each layer, what AgentCore and Foundry verifiably give you versus what stays your design, and how deletion requests reach agent memory.

Content current as of 2026-09.

Lessons

1. The tenancy threat model: four ways data bleeds
2. Isolation boundaries, layer by layer
3. What the platform gives you — and what stays your design
4. Quotas and noisy neighbours
5. Residency, deletion, and choosing an architecture