Troubleshoot Amazon Lambda deployment issues - Amazon CodeDeploy
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Troubleshoot Amazon Lambda deployment issues

Amazon 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 Amazon Lambda console to make sure the function is not configured to shift traffic between two versions:

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Lambda console at

  2. From the left pane, choose Functions.

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

  4. From Qualifiers, choose the alias used in your 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 Version.

  6. Choose Save and test.

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