- Newest
- Most votes
- Most comments
I am facing the same issue on the newly created AWS accounts. We created the new AWS accounts for production. I got below response from the support team when I asked them about the issue. I don't know why AWS is doing this. There is no issue in the existing accounts.
Your account is still too new to access the full capacity of Lambda. It's recommended to new customers to use their account for up to six months before querying capacity access issues. I appreciate your patience while this issue was reviewed and I trust that it gives you more clarity on next steps. Thank you for choosing AWS!
Can you check your quotas?
Service Quotas -> AWS services -> AWS Lambda -> Function memory maximum
Mine is set to 10GB but maybe yours got set to 3GB some time in the past.
Thanks for your response, it's set to 10,240MB. Other ideas?
I gave the same answer also in this post
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)
Trying making changes to the AWS Lambda function using the AWS Management Console, that will help eliminate probable suspect areas.
Which changes for example? Changing the timeout or memory via the Management Console didn't work
Also tried to download and redeploy the zip package through the Console, still the same error when trying to increase memory size
Relevant content
- asked 2 years ago
- asked 2 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Hi, couple of questions?
UPD: I tried myself to upgrade a lambda memory to 8 GB for an outdated environment and it worked. So outdated environment is not a problem
@AWS-User-6196864 it's in us-east-2, not @Edge, and the runtime is python3.8
Any news on this? I do have the same problem here for runtime python 3.8 and regio eu-central-1. The account's quota for lambda functions is set to 10 GB. I checked other runtimes as well but see the same error.
Similar problem. Using CDK 1.148, recently bootstrapped account, ap-southeast-2, node runtime 14. Deploying Lambdas with memory set to 4 GB. Account quota says it can be 10 GB. Dropping the Lambda memory to 3008 worked.
Same here, python3.8 in ap-southeast-2. Quotas are OK, AWS console raises the same error.