tenant
One customer organisation in a system shared by many, whose data must be kept separate from everyone else's.
In more detail
Tenants usually share infrastructure, so every store, query and log must carry the tenant boundary. Putting the tenant in keys and prefixes makes it possible to separate, grant and delete one customer’s data without touching others.
Example
images/tenant-a/avatar.png keeps one tenant’s objects under their own S3 prefix.Related terms
- key prefix — The leading part of an S3 object key, such as reports/2026/, which makes keys look like folders without creating real ones.
- partition key — The DynamoDB attribute whose value decides which storage partition an item lives in, and which every query must name.
- tenancy — Whether your virtual machine shares physical hardware with other customers (shared) or runs on hardware reserved for you (dedicated).
- confused deputy problem — An attack where a trusted program with broad access is tricked into using that access on behalf of someone who should not have it.
- Microsoft Entra ID — Microsoft's cloud identity service, formerly Azure Active Directory, which holds users and groups and signs people in to Azure and other apps.
- quota — A total allowance of use over a long period, such as a number of requests per day or month.
- noisy neighbor — One tenant or client that uses so much of a shared resource that others on the same system suffer.
- blast radius — How much of a system is affected when something fails or has to be running for a check to happen.
- assertion function — A function whose return type is asserts condition or asserts val is Type, which throws if the check fails and otherwise narrows the caller's code.
- authentication — Establishing who a request represents, for example by checking a password, a session cookie or a signed token.
Taught in
- S3: Buckets and Objects — Cloud Infrastructure & Hyperscaler Architecture
- Observability with CloudWatch — Cloud Infrastructure & Hyperscaler Architecture
- Shared Responsibility Model & Cloud Threat Landscapes — Cloud Security & DevSecOps Engineering
- AWS Organizations, Account Hierarchies & Azure Management Groups — Cloud Security & DevSecOps Engineering
- Cross-Account AssumeRole Chains & Temporary STS — Cloud Security & DevSecOps Engineering
- Partitioning, Sharding And Hot Keys — Scalable System Design & Distributed Architecture
- Load Balancing And The Failure Modes It Introduces — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
- Worked Design Three: Scaling The Metrics Pipeline — Scalable System Design & Distributed Architecture
- Optional Properties, Readonly And Index Signatures — Production TypeScript
- Union Types, Intersections And Property Conflicts — Production TypeScript
- Assertion Signatures: asserts condition And Invariants — Production TypeScript