Skip to content

Request for help nudging unassigned Support Case (Lambda memory limit increase) - Case ID: [***************]

-2

Hi AWS Community and Support Team,

I submitted an Account Support case 24 hours ago regarding a Lambda memory quota restriction on a new testing account (Case ID: [[***************]]). Currently, the case remains in the unassigned state.

I fully understand and respect that I am on a Basic Support plan, and that paid support tiers (Developer, Business, Enterprise) naturally and correctly take priority in the queue. I also appreciate that the support teams manage a high volume of requests on a daily basis.

The reason I am reaching out here is that I am simply trying to deploy an official AWS Solutions template (Media2Cloud). This template automatically provisions machine learning Lambdas that require more than the 3,008 MB memory safety limit placed on my account. Having read through several community threads, I noticed that some basic support users have unfortunately gotten stuck waiting 10 to 15+ days for simple account guardrail and limit adjustments.

I am hoping to avoid getting stuck in a long delay for what is a standard deployment prerequisite. If an AWS community manager or moderator happens to see this post, I would be deeply grateful if you could take a quick look or help nudge the ticket internally so I can proceed with my deployment.

Thank you very much for your time and assistance!

Edit: Removed case ID — Elle G.

3 Answers
2

I understand you're waiting for a Lambda memory limit increase to deploy the Media2Cloud solution. While I can't directly intervene in your support case status, I can offer some guidance on your situation.

For Lambda memory configuration limits, AWS accounts do have default service quotas that can be adjusted. The standard maximum memory allocation for Lambda functions is 10,240 MB, but new accounts may have lower limits initially as a protective measure.

Regarding your support plan, you're correct that response times vary by support tier. With a Basic Support plan, account and billing support is included, but technical support cases and service limit increases may experience longer response times compared to paid support plans. If you frequently need faster responses for technical issues or service limit increases, you might want to consider upgrading to a Developer, Business, or Enterprise Support plan, which offer faster response times and additional support channels.

For your immediate situation, the best course of action is to continue monitoring your case through the AWS Support Center at https://console.aws.amazon.com/support/. You can add additional correspondence there if you need to provide more context about your use case, which may help expedite the review.

If you find that you regularly encounter situations requiring quick service limit adjustments or technical guidance, reviewing your AWS Support plan options could provide you with the response times that better match your deployment needs. Different support tiers offer different response time commitments for various case severity levels.

answered 24 days ago

AWS
EXPERT

reviewed 24 days ago

AWS
SUPPORT ENGINEER

reviewed 24 days ago

0

Hello,

I've located your case and shared your concerns with our team for review.

If you've additional thoughts you'd like to mention, you can add them to your case for our team's visibility: Support Center

- Elle G.

AWS
EXPERT

answered 24 days ago

EXPERT

reviewed 23 days ago

  • Hey Elle G,

    Quick update on my support case:

    I did receive a response from support, and they unfortunately denied the request. The agent stated:

    Your request to increase the Lambda memory limit to 10,240 MB for account 049793667712 in us-east-1 will not be approved at this time.

    New AWS accounts are assigned reduced concurrency and memory quotas for Lambda. AWS raises these quotas automatically based on your usage — this is not a quota Support can override manually or grant an exception for. Reference: https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html"

    However, I found an older AWS re:Post thread (answered by an AWS expert and reviewed by two others) which explicitly states that because this limit isn't in the Service Quotas console, opening an Account and Billing case is the correct way to have this manually confirmed and increased: https://repost.aws/questions/QUvGzdNjQZQ9S3YDwvWVWpFw/lambda-function-memory-increase

    I am currently stuck in a Catch-22:

    1. Support is asking me to demonstrate 90% usage before they will increase the limit.
    2. I cannot generate any usage because the official Media2Cloud CloudFormation template hardcodes its ML Lambdas to require more than 3,008 MB of memory. The stack immediately fails and rolls back.

    Since we are an established business just trying to build out a Proof of Concept (PoC) in a safe, isolated sandbox account, does anyone know if a case like this can be escalated?

0

Hi Alex,

I'm sorry to hear about the difficulties you're facing with this. I've shared your situation internally, and it looks like some updates have been added to your case. Check your Support Center for the latest: Support Center.

- Rick N.

AWS
EXPERT

answered 23 days ago

EXPERT

reviewed 18 days ago

  • Hi Rick,

    Thank you so much for escalating this internally and getting back to me! I really appreciate your help.

    I did see the update in the Support Center yesterday at 15:58 GMT. The agent let me know: "Our service team has approved and processed your service quota increase request. It will be available within the next hour."

    However, I waited about 6 hours to ensure the change had plenty of time to propagate. When I re-attempted to deploy the stack, it unfortunately failed and rolled back with the exact same error: 'MemorySize' value failed to satisfy constraint: Member must have value less than or equal to 3008.

    I replied to the support case last night at 22:20 GMT to let the team know it was still failing. Could you please ask the internal team to take another look at this? It seems like the limit increase might be stuck on the backend, or perhaps it was accidentally applied to the wrong region (I am deploying in us-east-1).

    Thank you again for your ongoing help in getting this unblocked!

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.