- Newest
- Most votes
- Most comments
To give a more recent answer to this: I had the same error (13 month old account, fresh out of free tier, basic plan, Frankfurt / eu-central-1 region, Dotnet 6). The problem got resolved with the AWS support. Because technical support was not possible in my support tier, I filed a request in the Support Center as: Account & Billing, Service: "Account", Category: "Other Account Issues", Severity: "General Question". I have chosen "Chat" as communication method. After a short chat, a request was filed (at 9-10 am local time), and resolved (6am the following day).
Now I can set the memory limit to 10,240MB without issues. Tested in Frankfurt and Ireland region.
(Sorry for the lengthy answer, but maybe it saves someone a few minutes piecing together information)
Lambda functions with memory configuration greater than 3GB are currently unavailable for first time use in some regions. We are working on restoring this feature and mitigations are in progress. If you urgently require to use your function with memory greater than 3GB, please raise a support ticket and request that the limit get raised for your account.
Hi, was this fixed? Im still getting this error in my free-tier account in us-east-1
There is no way to request a quota increase through the service console since the "Function memory maximum" incorrectly shows the maximum of 10,240 megabytes already. Can you please provide instructions as to how one should go about contacting AWS support without paying for a support plan?
this seems to still be a problem, and you cannot raise a support ticket without a support plan of course, this is quite a pain!
If your account quota shows 10GB, and you are getting this error, it could be a service glitch or capacity issue.
You can either try again later, or choose another supported region and try again.
Thanks Jason, I tried another region (us-east-1) and did not receive the error. I also tried changing a modifying a different lambda in the problematic region and received the error again, so it's clearly something wrong with the region. Thanks, I'm assuming I'll need to reach out to support on this
Harrison - as Brettski pointed out you can escalate to support and request a limit lift. Hope this get resolved soon.
Relevant content
- asked 2 years ago
- asked 7 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Have the same issue. eu-central-1 python 3.9
Same issue here! eu-central-1
Had the same issue in us-east-1. Tried again a few weeks later, it just worked. No idea what changed