What should I do if my Lambda concurrent execution limit increase request is taking too long?
Asked by
TechyNinja47
I've requested to increase my AWS Lambda concurrent execution limit from the default of 10 to 1,000, as my production environment is running into throttling issues. This is affecting my 7,000 daily active users who are experiencing errors daily. It's been 11 days since my request, and I haven't received any response yet. How can I effectively get help from AWS regarding this issue? My case ID is 176488807100754.
Answers
Actually, isn't the default limit 1,000? I checked the AWS docs, and they say it should be. Have you confirmed the specifics on your account? It might be worth double-checking!
Reply to this answer
I'm sorry it’s taking so long! I managed to find your case, but I can’t share specifics here. I suggest you request Support to reach out to you via phone or chat for quicker assistance. Keep an eye on your email for an update from them!
Reply to this answer
Is this a new account? Usually, increases via Service Quotas get approved in hours. A jump from 10 to 1,000 is quite large; you might consider smaller increments like 100, then 250, and so on. That could speed up approval since they might be hesitant about such a big jump.
Reply to this answer
Did you submit your request through the service quotas console? Those are typically processed automatically, and you'd usually get a fast response from a bot. If you opened a support case directly, it may take longer since you're relying on customer service, which is often slower unless you have a specific support plan.
Reply to this answer
A workaround could be to create a second account. This isn't ideal, but it's a hacky solution if you're in a jam!
CloudyAdventurer: That could work! But I wonder if running the servers on my own might be a better approach?
Reply to this answer
Add your answer
Answers are reviewed before publication.
QuickFixReader: Thanks for the tip! I'll try requesting support by phone to speed things up.