Object Storage limits and quotas explained
Kort antwoord
Three Object Storage limits have a platform default: 3 buckets per storage tier, 20 access keys per project, and a reserved quota of up to 500 TB. The bucket limit is a default an administrator can change. Whether the others can be raised is not documented, so ask Support if you need more. The rest, including the maximum size of a single object, is not published. When you hit one of those, the S3-compatible API returns an error naming the limit, and that is the authoritative answer at the moment it matters.
The defaults you start with
Every Object Storage account starts from the same platform defaults. They are set in the platform configuration rather than tied to a package you buy, and Worldstream can change them per account.
| Scope | Limit | Default |
|---|---|---|
| Storage tier | Buckets per storage tier | 3 |
| Project | Access keys per project | 20 |
| Account | Maximum reserved quota | 500 TB |
Read these as the value you get without asking for anything, not as the most the platform can do. If your design needs more buckets, more keys, or more reserved capacity than this, that is a conversation with support rather than a wall.
What a tier means here
Object Storage has two tiers and both are redundancy classes, not access-speed classes:
| Tier | What it protects against |
|---|---|
| Distributed Storage (standard) | Redundant servers, disks and network within one datacenter. Becomes read-only if that datacenter is lost. |
| Geo-Redundant Storage (premium) | Multi-site replication. Can survive a full datacenter outage. |
Both are currently offered in the eu-west-1 region, and you pick one per project when you create it. There is no cold or archive tier, so a bucket allowance "per tier" means per redundancy class, not per access class. Object Storage tiers and lifecycle goes into what that means if you are used to Amazon S3 storage classes.
Pay per use or Reserved quota
You choose a billing model on your first Object Storage project: Pay per use, or Reserved quota. Two things are worth knowing before you click.
- The choice applies to all your Object Storage projects from that point on. Switching later requires a support request.
- Pay per use requires an active credit card payment method on the account.
Reserved quota is where the 500 TB default applies. It is the largest quota you can reserve without asking, not a cap on how much data the platform will hold.
Rates are not listed in this knowledge base. For current pricing, see worldstream.com or open a support ticket.
Limits this page does not publish
Some figures people ask for are not documented anywhere this knowledge base can verify, so they are not stated here rather than guessed at. That includes:
- the maximum size of a single object, by single
PUTand by multipart upload; - the maximum number of objects or total size in one bucket;
- request-rate limits per bucket or per project, and what happens when you cross one.
Two things make this less awkward than it sounds. The S3-compatible API enforces these itself and returns an error naming the limit the moment you exceed it, so your tooling finds out before your users do. And if you need a number before you build, a support ticket gets you one.
Rules that apply to every bucket
These are fixed, they apply to every bucket, and they have nothing to do with your account size:
| Rule | Value |
|---|---|
| Bucket name length | 3 to 63 characters |
| Bucket name characters | Lowercase letters, numbers, dots and hyphens |
| Object Lock | Optional, set when you create the bucket, cannot be disabled afterwards |
| Usage figures | Appear on the project's Usage tab once buckets have been active for at least 10 minutes |
Object Lock is the one to think about up front. There is no way to turn it on later and no way to turn it off, so decide per bucket before you create it.
Asking for a higher limit
Open a support ticket from Portal, or mail support@worldstream.com if you cannot log in. Say which limit you want raised, to what, and what you are building, so the answer comes back in one round instead of three. The same ticket is the right route for the figures this page does not publish.