Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Unable to set Lambda memory over 3008MB

0

I have a Lambda with the following configuration:

Region: us-east-1 (N. VIrginia) Runtime: nodejs16 Inside my accounts service quotas, I can see that my maximum function size is 10240 (10gb).

However, attempting to update to anything beyond 3008MB results in the following error:

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

According to this post, N. Virginia is a supported region.

I have seen numerous other posts about this issue and I tried contacting AWS technical support but I do not have a support plan and I was told by the account support rep to post so here I am /shrug.

Thanks!

Topics
ServerlessCompute
Tags
AWS Lambda
Language
English
asked 3 years ago698 views
2 Answers
1
Accepted Answer

That link to a previous post about this covers it pretty thoroughly. As @Brettski-AWS mentions it's a known account-based issue.

Your Basic (free) support doesn't cover technical support but this is an Account issue so you can raise a support case for it. Please follow the approach another person on that previous post used:

I filed a request in the Support Center as: Account & Billing, Service: "Account", Category: "Other Account Issues", Severity: "General Question".

EXPERT
answered 3 years ago
EXPERT
reviewed 3 years ago
  • Joe Siefers
    3 years ago

    I did that but the account rep I got would not help and said I needed to post - I guess I can try again and hope I get someone willing to help.

  • Steve Kinsman EXPERT
    3 years ago

    The trick is to not raise it as a technical issue, and stress it's an account issue. Quote @Brettski-AWS, he's very high profile. I can't tell you his real name without checking with him first but let me know if you get stuck.

  • Joe Siefers
    3 years ago

    They were able to solve the issue - thanks!

0

Don't make my mistake, assume AWS lambda has a hard 3008 MB limit.

Spent a very confusing & frustrating month trying to get this resolved. My only viable solution was to migrate away from lambda (and AWS after this experience).

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content