Quotas and Service Limits Explained

Sooner or later a launch fails with a message about limits rather than money. The account is funded, the configuration is valid, and the provider still refuses. That is a quota, and quotas are one of the least discussed practical constraints in cloud infrastructure.

What a quota is

A quota is a ceiling the provider applies to how much of a given resource an account may use. Typical examples include the number of virtual CPUs you may run in a region, the number of addresses you may reserve, or how many instances of a particular family you may start.

Quotas exist to protect the platform from runaway automation and to manage capacity. They are not a judgement about you, and they are usually adjustable on request.

Three properties that catch people out

They are usually per region

A generous quota in one region tells you nothing about another. Teams that expand to a second region for resilience often discover the new region starts from a low default.

They are often per family, not per machine

Limits commonly apply to a class of hardware rather than to instances generally. Plenty of vCPU headroom for general-purpose machines does not imply any headroom for GPU-backed ones, which are frequently limited to zero by default.

They move with account history

Defaults for a brand-new account are conservative. Accounts with a longer record of normal usage and verified billing often carry higher ceilings. This is exactly why account maturity is described in listings: an upgraded or established profile is less likely to hit a wall on the first serious deployment.

Checking before you need it

Every major provider exposes current quotas and current usage in the console, usually under a name like service quotas or limits. The check takes a few minutes and is worth doing before a migration rather than during one.

Note three things: the limit, the current usage against it, and whether the limit is adjustable. That last point matters because a small number of limits are hard.

Requesting an increase

Increase requests are ordinary support requests. They succeed more often when they state the resource, the region, the target number and a short reason. They are not instant, so a request submitted the evening before a launch is a risk in itself.

Why this matters when taking over an account

Quota state is part of what you inherit, and it is invisible from the outside. Two accounts on the same provider can differ by an order of magnitude in what they will let you start on day one.

Listings that describe capacity, such as the vCPU-oriented AWS configurations or the OVHcloud vCPU profile, are describing this dimension. After any handover, confirm the current figures in the console rather than assuming they are fixed, because quotas can be adjusted by the provider in both directions. The wider set of first-day checks is in auditing an unfamiliar cloud account.