Menu
AWS CodeDeploy
User Guide (API Version 2014-10-06)

Troubleshoot AWS Lambda Deployment Issues

AWS Lambda deployments fail after manually stopping a Lambda deployment that does not have configured rollbacks

In some cases, the alias of a Lambda function specified in a deployment might reference two different versions of the function. The result is that subsequent attempts to deploy the Lambda function fail. A Lambda deployment can get in this state when it does not have rollbacks configured and is manually stopped. To proceed, use the AWS Lambda console to make sure the function is not configured to traffic shift between two versions:

  1. Sign in to the AWS Management Console and open the AWS Lambda console at https://console.aws.amazon.com/lambda/.

  2. From the left pane, choose Functions.

  3. Select the name of the Lambda function that is in your AWS CodeDeploy deployment.

  4. From Qualifiers, choose the alias used in your AWS CodeDeploy deployment.

  5. From Additional Version, choose <none>. This ensures the alias is not configured to shift a percentage, or weight, of traffic to more than one version. Make a note of the version selected in the Version drop-down menu.

  6. Choose Save and test.

  7. Open the AWS CodeDeploy console and attempt a deployment of the version displayed in the drop-down menu in step 5.