My account is capped at 3008 MB for Lambda function memory. When I attempt to set memory above 3008 MB, I receive this error:

Question

'MemorySize' value failed to satisfy constraint: Member must have value less than or equal to 3008

I need the account-level memory quota raised to 4096 MB in us-east-2.

Use case: I am running a U2-Net machine learning model (176 MB on disk) for product image segmentation inside a container-based Lambda function. The function processes e-commerce product photos for an online vintage clothing resale business.

Peak memory breakdown:
- U2-Net model loaded in memory: ~700 MB
- onnxruntime inference working memory: ~1,500 MB peak
- Python runtime + libraries (opencv, Pillow, numpy, boto3): ~400 MB
- Image buffers (original + resized + mask + output): ~200 MB
- OS and Lambda overhead: ~300 MB
- Total peak: ~3,100 MB

The function runs successfully up to the point of model inference, then is killed with a segmentation fault at 3008 MB because peak memory exceeds the cap by approximately 100 MB. 4096 MB provides the necessary headroom for reliable operation.

This is not a Service Quotas issue — the memory quota does not appear in the Service Quotas console. I understand this requires manual account-level review. But it's not being looked at. Is there another service outside o Amazon if I can't test this? Tired of wasting long hours on building stuff.

For reference I'm not a coder.

re:Post Agent · Answer

I understand your frustration with the memory limitation. The 3008 MB memory cap you're experiencing is actually a reduced quota that AWS applies to new accounts. This is a temporary account-level restriction, not the standard Lambda limit.

Standard AWS accounts can allocate up to 10,240 MB (10 GB) of memory to Lambda functions, in 1-MB increments. Your account appears to still have the new account restrictions in place.

Unfortunately, you cannot request memory quota increases through the standard Service Quotas console - this is correct. Memory quota increases for accounts with reduced limits require AWS Support intervention to review and remove the new account restrictions.

To resolve this, you'll need to:

1. **Open a support case with AWS Support** (if you have a support plan) specifically requesting removal of the new account memory restrictions for Lambda in us-east-2
2. **Provide your use case details** (which you've outlined well - the ML model inference requirements)
3. **Request the standard Lambda memory limit** of 10,240 MB be applied to your account

If you don't have an AWS Support plan, you may need to wait for the new account restrictions to be automatically lifted over time as your account matures, or consider upgrading to at least a Developer support plan to open technical support cases.

The 4096 MB you need is well within Lambda's standard capabilities - you just need the new account restrictions removed. Once that happens, you'll be able to configure your function with the memory it requires for your U2-Net model inference workload.  
**Sources**  
[Troubleshoot deployment issues in Lambda - AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/troubleshooting-deployment.html)  
[Lambda quotas - AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html)

My account is capped at 3008 MB for Lambda function memory. When I attempt to set memory above 3008 MB, I receive this error:

Add your answer

Relevant content