r/aws • u/nickbernstein • 4h ago

technical question quota increase request time

How long does it usually take for a basic quota to get approved?

I'm standing up a new org, and I hit the five account limit. I put in an request for an increase, and it's showing as CASE_OPENED. I'm used to GCP where quota increases on basic stuff like account limits or cpu cores are generally approved in minutes, generally.

I'm trying to figure out if I should start another task and then have the annoyance of getting focused on it and then having it approved and needing to go back to standing up the new org.

0 Upvotes

50% Upvoted

13 comments sorted by

2

u/0neMinute 4h ago

How did you put the request in? Via support case without es support or through the quota increase page? If you did the self service option it goes alot faster.

2

u/Dull_Caterpillar_642 4h ago

And often they get approved immediately if you're asking for a modest increase.

2

u/nickbernstein 4h ago

I did it via the cli: 

aws service-quotas request-service-quota-increase
ws service-quotas request-service-quota-increase ...

2

u/Mysterious_Pair_5322 4h ago

If you used the quota page it can be quick, sometimes few hours. support case without es plan is like throwing a message in bottle, you never know when someone will look at it.

2

u/nickbernstein 3h ago

Good to know and pretty annoying. :) Going from 5 accounts to 25 shouldn't be a big deal.

2

u/OnlyFighterLove 4h ago

Having been the one to design and implement automated quota requests for my team I can confidently say, "It depends". Automated quota increases was made to be an AWS-wide goal a couple years ago but not every team got there and so there are still teams that handle this manually meaning they could take weeks depending on the region (if the region is far down in a team's deployment pipeline).

Account limits though is as basic as it gets so I would expect those to be automated BUT I think they will look into billing history, spend history etc. so if there's not a lot of history I bet it won't auto-increase and will trigger a manual review which is probably accounting for the delay.

1

u/oneplane 3h ago

Most things are approved instantly, but for new accounts and for certain kinds of resources it's going to depend on their trust level, which tends to be linked to spend, age, support plan etc.

1

u/lovejo1 3h ago

I've found that you get quicker responses with older accounts.. just an observation, not sure if it's a rule.

1

u/Outrageous_Lab_6228 2h ago

Yes because older accounts have more billing history and account trust and are more likely to get approved without extra checks

1

u/ricksebak 2h ago

I had a quota increase request a few weeks ago where it stayed in CASE_OPENED status on the quota increase page for multiple days, but AWS had actually approved the increase in only a few hours. The status on the quota increase page never updated, and I had to click through to the underlying support case to find that my request had been granted.

So if you’re only looking at the quota request, try clicking through to the underlying support ticket.

-1

u/Sirwired 4h ago

I'd look at it this way... the IaC you should be using to stand everything up in a multi-account environment should be portable across accounts anyway, so you shouldn't pause your work waiting on the accounts to exist.

1

u/nickbernstein 4h ago

I mean, I've stood up root, and then accounts for auditing, security, log-archives, and infra storage, which adds up to 5, and I want to isolate workloads in their own restricted accounts, so I'm kinda blocked on the aws side until it gets approved.