6MB AWS Lambda Hard Limit Strikes Again
See original GitHub issueThis is a Bug Report
Description
For bug reports:
- What went wrong?
When attempting to use
npm i npm --save
failed.
It actually came about attempting to install cordova
as npm is a dependency of it.
-
What did you expect should have happened?
npm
module should have installed -
What stacktrace or error message did you experience?
Similar or dependent issues:
Additional Data
- NPM CLI version you are using: 3.10.16
- Serverless version you’re using: 1.6.1
- Node version you’re using: v6.2.0
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Lambda quotas - AWS Documentation
Maximum sizes, limits, and quotas for Lambda functions and API requests. ... 6 MB each for request and response (synchronous). 256 KB (asynchronous)....
Read more >Hit the 6MB Lambda payload limit? Here's what you can do.
Turns out you can't POST more than 6MB of data to Lambda through API Gateway. Maybe Winston can lose a few pixels as...
Read more >AWS Lambda Limitations in Real-Life Applications - Medium
There is a hard limit of 15 minutes of execution per call for each lambda. So if you are planning to get some...
Read more >AWS Lambda Limits - Lumigo
AWS Lambda size limit is 50 MB when you upload the code directly to the Lambda service. However, if your code deployment package...
Read more >Laravel Vapor + DynamoDB queued Job + 120 MB json feed ...
There is a hard limit of 6mb when it comes to AWS Lambda payload size. This means we cannot send more than 6mb...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to bypass this, specifically for the package ‘npm’, by forking the code and changing the response of the package-get be a redirect, instead of directly fetching its meta, when fetching NPM packages.
@micksabox AWS Lambda limits response body payload (e.g., your npm package) to 6MB
https://docs.aws.amazon.com/lambda/latest/dg/limits.html