-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loopback Server and AWS Lambda hard limit #2
Comments
Happy New Year @PerfectedTech ! Supposedly the AWS Lambda storage limit can be increased, as referenced in the corresponding documentation. That said, I never asked for a storage limit increase so I cannot confirm it is possible or how high it might go. If I had to tackle this issue, here are the steps I would experiment with (in no particular order):
Please let me know in case you run into issues with the process above and I would be willing to help (time permitting). In particular I have been considering adding the Lambda layers example to this repo but did not want to make it overly complicated for those uninitiated in AWS Lambda. So if it helps you I could look into adding a layer sample to this repo or creating a new repo for the layer sample (and maybe even use the dependencies for your current project if they are public). |
Hi @marcelobern, Thank you very much for your detailed reply. I reached out to AWS asking them to increase the limit, but it turns out that the application unzipped cannot be more than 250MB. They suggested breaking the application into smaller parts and invoking lambda from one another. Not sure that would be the best practice with the structure that Loopback provides. If I come by any other approach to the problem, I will certainly update here. All the best and happy new year, Alexander |
@PerfectedTech thanks for the update! Breaking the application definitely makes sense to me. The one word of advise is to make sure you are using a cost effective way to do that, so your Lambda/API Gateway/etc. costs do not end up being higher than running a loopback server straight out of EC2 (or the like). Here are some thoughts that come to mind related to loopback, Lambda, and serverless in the context of solving this issue:
I will close the issue and pin it so others with a similar issue can easily benefit as you post updates ;-) |
Lovely work, botbits!
Just curious how one may handle a loopback server that is more than 250 megs due to dependencies and etc. AWS Lambda has a hard limit of 250 megs.
The text was updated successfully, but these errors were encountered: