There is a specific moment familiar to anyone who has opened a fresh AWS account with a deadline attached: everything works, the console loads, and the instance you actually need refuses to start.
A quota is a ceiling, not a budget
The single most common misunderstanding is treating a vCPU quota as a monthly allowance. It is not. It caps how much compute may run at the same instant.
Run one 32-vCPU instance and you have consumed a 32-vCPU quota entirely, for as long as it is up. Run four 8-vCPU instances and you have done exactly the same thing. Nothing is being “used up” over time — you are simply not permitted to exceed the ceiling at any given moment.
Why the ceiling is so low to begin with
New accounts get conservative quotas because AWS has no history with you, and abuse — crypto mining above all — arrives on new accounts at scale. It is a defensible policy that happens to make a brand-new account useless for real work on day one.
You can file an increase. It may take days. It may be refused without a reason you can act on. Neither outcome cares about your sprint.
Where it bites: the deploy
Here is the detail that catches people. A rolling deployment briefly runs the old and the new fleet simultaneously. If your steady state sits just under the ceiling, your deploy will not — and the failure arrives mid-release, in front of an audience.
How to size it in five minutes
- List everything concurrent. Production, staging, CI runners, workers, cron, batch jobs.
- Sum the peaks, not the averages. Averages conceal precisely the moment that breaks you.
- Add about 30% headroom for spikes and deploy overlap.
- Round up to a real tier. Under 32? Take the 32 vCPU account and stop optimising.
The regional trap
Quotas are granted per region. A 64 vCPU ceiling in Frankfurt gives you exactly nothing in Virginia. Discovering this mid-migration is a genuinely bad afternoon, and it is the most common expensive mistake in cloud procurement.
And the thing quota does not fix
If your instances launch fine and the bill is what hurts, quota is irrelevant to you. That is a cost problem, and the answer is credit, not concurrency. Here is how to tell which you have.
Leave a Reply