AWS Lambda just got a major upgrade

Ever run into the infuriating 75 GB code storage limit AWS Lambda puts on your deployment artifacts?

No longer will this limitation stop you from loading up your serverless codebases with everything and the kitchen sink(for good or for bad).

To be clear, the 250 MB (unzipped) per lambda still exists. The 75GB is on an account level, not per lambda level.

In their own words: Lambda reads your code directly from your bucket, eliminating quota pressure and giving you full security control.

This sounds amazing, but I am also curious how this will affect deployment time and cold boot durations.

I was concerned, but the people at AWS directly state that it will be a non-issue:

Using self-managed S3 buckets also results in a faster time to first invoke for new functions and after function updates, because Lambda no longer needs to copy your zip package to a Lambda-managed S3 bucket.

This makes sense as we don’t need to rebuild the base image, just pull the codebase into the running Lambda.

Another feature of this is that you can use all the encryption features in S3 to keep your Lambda code extra secure. This would likely be most valuable in a situation that requires security compliance.

It’s funny how Lambda has evolved from a tiny function runner to being able to do anything and everything under the sun.

My question for you:

Is that a good thing or a bad thing?

Are you all in on serverless or not? Let me know your reasoning.