Skip to content

Error when testing Lambda: "Lambda was not able to unzip the file"

0

After uploading a .zip containing code for my Lambda, I tried to test it using Lambda's built-in testing functionality. However, I get the following error:

Calling the invoke API action failed with this message: Lambda was not able to unzip the file

I can unzip the file locally with unzip lambda.zip, and running unzip -l lambda.zip shows that it contains the a handler.js as expected. I can even view the source code for the Lambda in the AWS console on the Lambda's Code tab.

It seems as though the Lambda runtime might be using a different (and broken?) way of decompressing ZIP archives?

asked 3 years ago2.6K views
2 Answers
0

How large is your ZIP file? If it is more than 50 MB (compressed) or 250 MB (uncompressed) it exceeds the service limits. If you are exceeding that size, consider using a container image.

AWS
EXPERT
answered 3 years ago
  • Thanks for sharing your experience—this makes sense now. I didn’t even think to consider the uncompressed size, especially since the zip looked reasonable. I’ll double-check that and also make sure unnecessary folders like node_modules aren’t inflating it. Appreciate the heads-up!

0

That can be cause of size , as i just one time saw this error 5 years ago when packaging a large bundle which was self contained and larger that 250 MB unzipped , but i compressed that as 45M but i got this error

Check if you are not zipping the node_modules , or other heacy bundles

also verify if it s a real zip file

answered 3 years ago
  • Appreciate this—your mention of node_modules reminded me how bloated those folders can get. Easy to overlook how much weight we add with dependencies. Definitely a good reminder to trim the fat before packaging!

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.