Question

A developer is preparing to deploy a serverless application defined in an AWS CloudFormation template. The template references a Lambda function whose code lives in a local directory. When the developer tries to deploy with 'aws cloudformation deploy', the function's local code path is not accepted by CloudFormation. What is the correct step to prepare the deployment artifacts so the template can be deployed?

Accepted Answer

Run 'aws cloudformation package' to upload the local code to an S3 bucket and produce a processed template that references the S3 object, then deploy the output template.

Answer

Manually zip the code and paste the base64-encoded contents directly into the CloudFormation template's ZipFile property for the deployment.

Answer

Configure CodeDeploy to read the local directory at deploy time and inject the code into the Lambda function automatically.

Answer

Enable versioning on the target Lambda function so CloudFormation resolves the local path to the latest published version.