: When zipping entire directories, always exclude local environment folders (like venv/ or node_modules/ ) and version control metadata (like .git/ ) to keep the file size under the deployment limits [10].
: Use build scripts (like build.gradle or package.json scripts) to install dependencies into a temporary folder before the final ZIP command to ensure a "clean" environment [8]. [handler].zip
Once generated, the ZIP file is uploaded to the cloud provider. : When zipping entire directories, always exclude local
: Automatically packages files into a .serverless directory, often naming the primary artifact based on the function name, though it can be manually specified as handler.zip in the serverless.yml [8]. 4. Best Practices : Automatically packages files into a
A standard handler.zip package contains the source code and all necessary dependencies required for the function to execute. For a Python-based Lambda, the structure usually looks like this:
: Use the output_base64sha256 attribute in Terraform to ensure the ZIP file only triggers a redeployment when the underlying code has actually changed [10].
data "archive_file" "lambda_zip" { type = "zip" source_file = "${path.module}/src/handler.py" output_path = "${path.module}/dist/handler.zip" } Use code with caution. Copied to clipboard : Points to your raw script (e.g., src/handler.py ).