# Quotas for Object Storage

How many buckets and S3 access keys you can have and how much you can store on your own storage, and how to raise a quota.

(The table of quotas is generated on the web page.)
- A bucket or S3 access key over its quota is refused with `409` before anything is created; the
  message starts "Quota exceeded:" and names the quota, the limit and how many are in use. Buckets
  the platform manages (a database's backups, a Kafka cluster's tiered storage) do not count;
  temporary credentials do not count as access keys.
- The stored-data quota applies only to buckets on your organization's own storage (a storage
  cluster or own hosts). Past it, new data is refused with `403 QuotaExceeded`; reading and deleting
  always work.

## Raise a quota

Ask for a higher value of an adjustable quota, up to its ceiling:

1. Open **Service quotas** in the Deutsche Cloud Console.
2. In the quota's **⋯** menu, choose **Request increase**. It is unavailable for a fixed limit
   ("This limit is fixed") and while a request is open ("A request is already open").
3. In **Request a quota increase**, for **New value** (**New value (GiB)** for stored data),
   enter the value you need.
4. For **What you need it for**, enter the reason, then choose **Send request**.

This needs `quotas:RequestServiceQuotaIncrease`. With the CLI:

```sh
dcloud quotas requests request-increase --quota-id s3.buckets --requested-value 200 --reason "one bucket per customer"
```

An organization on trial quotas
is told to ask Deutsche Cloud support to move it to standard quotas instead.

## Related

- [Create a bucket](create-a-bucket.md)
- [Storage locations](storage-locations.md)
