# Quotas for Compute

How many instances, vCPUs, volumes, snapshots, images, networks, security groups, elastic IPs, NAT gateways and snapshot policies you can have, and how to raise a quota.

(The table of quotas is generated on the web page.)
A request over a quota is refused with `409` before anything is created. The error starts
`Quota exceeded:` and names the quota, the limit, how many are in use and how many more the request
needs; the body also carries `code: "QuotaExceeded"` and the numbers under `quota`. An organization
on trial quotas is told to ask support to move it to standard quotas. A launch holds its instance, its vCPUs and any launch volumes
together, so it never half-fits. The default network counts as a VPC. A resize to a bigger type
takes the extra vCPUs from the vCPU quota. Key pairs count toward the SSH key pairs quota of KMS.

## 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. On the quota's row, choose **Request increase**.
3. In **Request a quota increase**, for **New value**, enter the value you need.
4. For **What you need it for**, enter the reason, then choose **Send request**.

This needs `quotas:RequestServiceQuotaIncrease`. **Request increase** is unavailable for a fixed
limit and while a request for that quota is still open.

For an organization on standard quotas, a request for volume snapshots, machine images, VPCs,
subnets, security groups or snapshot policies of at most twice the standard default is approved at
once, unless one was approved that way recently. Other requests wait for review.

## Related

- [Launch an instance](launch-an-instance.md)
