A simple JSON-transform Lambda ships a 250 MB deployment package, s…

Question

A simple JSON-transform Lambda ships a 250 MB deployment package, slowing updates and cold starts. What should the developer do?

Accepted Answer

Shrink the deployment artifact, move heavy shared libraries into Lambda layers, and remove unused dependencies. — Hauling a 250 MB suitcase for a JSON tweak is why deploys crawl and cold starts sting. Trim unused libs, and park shared heavyweight code in layers. Maxing memory or stuffing zips into DynamoDB does not fix a fat package.

Answer

Upload the 250 MB zip to every Region manually before each one-line code change.

Answer

Increase memory to the maximum solely to hide package-size problems without trimming dependencies.

Answer

Store the deployment zip inside DynamoDB items larger than 400 KB as the primary artifact store.

A simple JSON-transform Lambda ships a 250 MB deployment package, slowing updates and cold starts. What should the developer do?

Short Explanation

Full Explanation