A municipal Lambda deployment package omits a native library that e…

Question

A municipal Lambda deployment package omits a native library that exists on a developer's laptop, so production invocations crash on import even though local tests pass. What should the team ensure when preparing the artifact?

Accepted Answer

Package all required runtime dependencies in the deployment zip or a Lambda layer that matches the Lambda OS/architecture — If it only works on your laptop, it is not packaged — Lambda's OS never saw that native .so. Bundle the dependency in the zip or a matching layer before you call it "deployed."

Answer

Ship only the handler .py file and assume the Lambda managed runtime includes every native library from developer laptops

Answer

Rely on the developer's local virtualenv path remaining valid inside the Lambda execution environment

Answer

Exclude native dependencies from the zip to stay under size limits and load them from the public internet at cold start

A municipal Lambda deployment package omits a native library that exists on a developer's laptop, so production invocations crash on import even though local tests pass. What should the team ensure when preparing the artifact?

Short Explanation

Full Explanation