How to enable a bucket quota in e3 Object Storage
Bucket quotas let you put hard limits on a specific bucket, so it can’t grow forever (accidentally or otherwise). Once a quota is enabled, uploads and writes are rejected when the limit is exceeded—ideal for cost control, tenant isolation, and preventing runaway jobs.
What is a bucket quota?
A bucket quota is a limit applied to one bucket in e3 Object Storage. You can set quotas based on:
Storage amount (how much data the bucket can hold), and/or
Object count (how many objects/files can exist in the bucket)
You can use either one, or both together.
Where to find bucket quotas in the dashboard
You’ll enable quotas from the bucket’s Management tab.
Navigation: e3 Object Storage → Buckets → (select a bucket) → Management → Gear icon
Open e3 Object Storage in the dashboard.
Find the bucket you want to limit.
In the Bucket quota section, click the Gear icon (⚙️).
In the drawer, tick Enable bucket quota.
Set either (or both) limits:
Max storage: enter a number and choose a unit (ex: GB, TB)
Max objects: enter the maximum number of objects allowed
Close the drawer. Your settings apply immediately.
Setting a storage quota (Max storage)
Use this when you want to cap the bucket by size (ex: “This bucket can’t exceed 500 GB”).
In Max storage, set a value (example: 500)
Choose the Unit (GB/TB/etc.)
Setting an object quota (Max objects)
Use this when you want to cap how many “things” can be stored (even if they’re small).
In Max objects, set a value (example: 1,000,000)
Good for: buckets that store lots of tiny files, API logs, thumbnails, versioned objects
What does “-1” mean?
In the quota drawer you’ll see -1 by default.
-1 = unlimited (no limit)
So:
If you only want a storage limit, leave Max objects at -1
If you only want an object limit, leave Max storage at -1
If you want both, set both to real numbers
What happens when the quota is reached?
When a bucket hits its quota:
New uploads/writes are rejected
Existing objects remain accessible (reads still work)
Deleting objects (or reducing usage) will allow writes again once you’re back under the limit