AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
How to increase Lambda memory above 3008 MB
Hey,
We are getting the following:
RequestId: 55caface-5698-5285-80dc-9a64dc03ff72 Error: Runtime exited with error: signal: killed
Runtime.ExitError
END RequestId: 55caface-5698-5285-80dc-9a64dc03ff72
REPORT RequestId: 55caface-5698-5285-80dc-9a64dc03ff72 Duration: 10677.99 ms Billed Duration: 10678 ms Memory Size: 3008 MB Max Memory Used: 3008 MB
And when I try update the memory usage I get the following:
I get the same error when using the CLI too.
It shows on the GUI that we can go to 10GB but it seems to cap us at 3GB. How can we actually get the full 10GB?
N.B. I have already seen:
- https://repost.aws/questions/QUE2zujNt7SVWBrwR34SZpYQ/memorysize-value-failed-to-satisfy-constraint-member-must-have-value-less-than-or-equal-to-3008
- https://repost.aws/questions/QUKruWYNDYTSmP17jCnIz6IQ/unable-to-set-lambda-memory-over-3008mb But these are old now and that support method is no longer possible.
- Newest
- Most votes
- Most comments
The issue you're experiencing is due to an account-specific memory limit for Lambda functions set to 3008 MB (approximately 3 GB). While AWS Lambda functions can theoretically use up to 10,240 MB (10 GB) of memory, individual AWS accounts may have lower limits applied.
To increase your Lambda function's memory limit beyond 3008 MB, you'll need to request a quota increase from AWS Support. Here's how to do it:
- Open a case with AWS Support.
- Make sure to open the case under the "Account and billing" category, not as a technical support issue.
- In your support case, explain that you need to increase the memory limit for your Lambda functions beyond the current 3008 MB limit.
It's important to note that you cannot increase this limit through the standard Service Quotas console. AWS Support needs to review and approve these requests manually.
Even though AWS documentation states that new accounts have reduced quotas that are automatically raised based on usage, this isn't always the case, even for accounts that have been around for some time. By contacting AWS Support directly, you can have them review your account's specific situation and potentially increase your Lambda function memory limit to meet your needs.
Remember that increasing the memory allocation for a Lambda function also proportionally increases the amount of CPU, which can significantly improve performance for memory-intensive or CPU-bound operations. Once AWS Support increases your limit, you should be able to configure your Lambda functions with memory sizes up to 10,240 MB as needed.
Sources
'MemorySize' value failed to satisfy constraint: Member must have value less than or equal to 3008 | AWS re:Post
AWS Lambda memory limit seems to be too low | AWS re:Post
Configure Lambda function memory - AWS Lambda
answered a year ago
The memory setting for Lambda has to be proportional to CPU settings. That is, if you increase the memory setting, you also need to increase the CPU. I cannot see the CPU setting in your screen shot, I am assuming it's much lower. Increase you CPU setting as well, and see if it fixes the issue.
Relevant content
asked 10 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
Hi @Shajam, in AWS Lambda, you don't directly increase CPU settings. Instead, CPU power is proportionally allocated based on the amount of memory you allocate to your function. Unless you know of a way to directly increase the CPU setting? Please let me know.
My bad, you are absolutely correct. Lambda only has memory configuration setting.