multi-tenant-isolation
Multi-Tenant Isolation on AWS
Tenant isolation is the architectural decision a SaaS startup is least able to reverse and most likely to get wrong under time pressure. Getting it wrong produces either a cross-tenant data leak, which is an existential incident for a company selling to businesses, or a per-tenant cost floor that makes the unit economics never work.
The mistake is treating it as one decision. It is a decision per layer, and the layers can differ.
Choose a model per layer, not per application
| Model | What it means | Isolation | Cost per tenant | Where it fits |
|---|---|---|---|---|
| Silo | Dedicated resource per tenant | Strongest, enforced by resource boundary | Highest, floors multiply | Regulated or contractual isolation, or one customer large enough to fund it |
| Pool | Shared resource, logical separation | Weakest, depends on your correctness | Lowest, marginal per tenant | Default for most tenants, especially self-serve |
| Bridge | Shared infrastructure, dedicated slice inside it | Middle, enforced by partition | Low to medium | Pooled compute with per-tenant schema or table |
Pick per layer. A common and correct shape: pooled compute, bridge-model database (schema or partition key per tenant), siloed only for the customer whose contract requires it.
The trap. Going full silo because it is easier to reason about, then discovering the fixed floors multiply by tenant count. Each dedicated Aurora Serverless v2 cluster carries a floor around 0.5 ACU whether or not the tenant is active. Each OpenSearch Serverless collection carries a substantial monthly minimum. Ten silo tenants on floored services is a large bill for near-zero usage. Verify current minimums with the aws-billing-and-cost-management skill in aws-core before committing to a silo model, since these change.
The other trap. Going full pool and enforcing isolation with a WHERE tenant_id = ? clause in application code. That makes every future query a potential cross-tenant leak, and the blast radius of one missing predicate is every customer.