Updating an Amazon ECS blue/green deployment using the console - Amazon Elastic Container Service
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 (PDF).

Updating an Amazon ECS blue/green deployment using the console

You can update a blue/green deployment configuration using the Amazon ECS console. The current blue/green deployment configuration is pre-populated. You can update the following blue/green deployment options:

  • Deployment group name - The CodeDeploy deployment settings

  • Application name - The CodeDeploy deployment group

  • Deployment configuration - How CodeDeploy routes production traffic to your replacement task set during a deployment

  • Test listener on the load balancer - CodeDeploy uses the test listener to route your test traffic to the replacement task set during a deployment

You must configure the new option before you update the configuration.

To update a blue/green deployment configuration (Amazon ECS console)
  1. Open the console at https://console.amazonaws.cn/ecs/v2.

  2. On the Clusters page, select the cluster.

  3. On the Cluster overview page, select the service, and then choose Update.

  4. Expand Deployment options - Powered by CodeDeploy, and then choose which options to update:

    • To modify the CodeDeploy deployment group, for Application name, choose the deployment group.

    • To modify the CodeDeploy deployment settings, for Deployment group name, choose the group.

    • To modify how CodeDeploy routes production traffic to your replacement task set during a deployment, for Deployment configuration, choose the option.

  5. Select the deployment lifecycle event hooks and the associated Lambda functions to run as part of the new revision of the service deployment. The available lifecycle hooks are:

    • BeforeInstall – Use this deployment lifecycle event hook to invoke a Lambda function before the replacement task set is created. The result of the Lambda function at this lifecycle event does not initiate a rollback.

    • AfterInstall – Use this deployment lifecycle event hook to invoke a Lambda function after the replacement task set is created. The result of the Lambda function at this lifecycle event can initiate a rollback.

    • BeforeAllowTraffic – Use this deployment lifecycle event hook to invoke a Lambda function before the production traffic has been rerouted to the replacement task set. The result of the Lambda function at this lifecycle event can initiate a rollback.

    • AfterAllowTraffic – Use this deployment lifecycle event hook to invoke a Lambda function after the production traffic has been rerouted to the replacement task set. The result of the Lambda function at this lifecycle event can initiate a rollback.

  6. To modify the test listener, expand Load balancing, and then for Test listener for CodeDeploy deployment, choose the test listener.

  7. Choose Update.