Create an application for a blue/green deployment (console)

To use the CodeDeploy console to create an application for a blue/green deployment:

Note

A deployment to the AWS Lambda compute platform is always a blue/green deployment. You do not specify a deployment type option.

Warning

Do not follow these steps if:

• You do not have instances with the CodeDeploy agent installed that you want to replace during the blue/green deployment process. To set up your instances, follow the instructions in Working with instances for CodeDeploy, and then follow the steps in this topic.

• You want to create an application that uses a custom deployment configuration, but you have not yet created the deployment configuration. Follow the instructions in Create a Deployment Configuration, and then follow the steps in this topic.

• You do not have a service role that trusts CodeDeploy with, at minimum, the trust and permissions described in Step 2: Create a service role for CodeDeploy. To create and configure a service role, follow the instructions in Step 2: Create a service role for CodeDeploy, and then follow the steps in this topic.

• You have not created a Classic Load Balancer, Application Load Balancer, or Network Load Balancer in Elastic Load Balancing for the registration of the instances in your replacement environment. For more information, see Set up a load balancer in Elastic Load Balancing for CodeDeploy Amazon EC2 deployments.

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

   Note

   Sign in with the same user that you set up in Getting started with CodeDeploy.

2. In the navigation pane, expand Deploy, and then choose Getting started.

3. In Application name, enter the name of your application .

4. From Compute platform, choose EC2/On-Premises.

5. Choose Create application.

6. On your application page, from the Deployment groups tab, choose Create deployment group.

7. In Deployment group name, enter a name that describes the deployment group.

   Note

   If you want to use the same settings used in another deployment group (including the deployment group name tags, Amazon EC2 Auto Scaling group names, and the deployment configuration), choose those settings on this page. Although this new deployment group and the existing deployment group have the same name, CodeDeploy treats them as separate deployment groups, because each is associated with a separate application.

8. In Service role, choose a service role that grants CodeDeploy access to your target instance.

9. In Deployment type choose Blue/green.

10. In Environment configuration, choose the method to use to provide instances for your replacement environment:

    1. Automatically copy Amazon EC2 Auto Scaling group: CodeDeploy creates an Amazon EC2 Auto Scaling group by copying one you specify.

    2. Manually provision instances: You won't specify the instances for your replacement environment until you create a deployment. You must create the instances before you start the deployment. Instead, here you specify the instances you want to replace.

11. Depending on your choice in step 10, do one of the following:

    • If you chose Automatically copy Amazon EC2 Auto Scaling group: In Amazon EC2 Auto Scaling group, choose or enter the name of the Amazon EC2 Auto Scaling group you want to use as a template for the Amazon EC2 Auto Scaling group for the instances in your replacement environment. The number of currently healthy instances in the Amazon EC2 Auto Scaling group you choose is created in your replacement environment.

    • If you chose Manually provision instances: Enable Amazon EC2 Auto Scaling groups, Amazon EC2 instances, or both to specify instances to add to this deployment group. Enter Amazon EC2 tag values or Amazon EC2 Auto Scaling group names to identify the instances in your original environment (that is, the instances you want to replace or that are running the current application revision).

12. In Load balancer, select Enable load balancing, and then from the lists, select the Classic Load Balancers, Application Load Balancer target groups, and Network Load Balancer target groups that you want to register your replacement Amazon EC2 instances with. Each replacement instance will be registered with all the selected Classic Load Balancers and target groups. You can select up to 10 Classic Load Balancers and 10 target groups, for a total of 20 items.

    Traffic will be rerouted from the original to the replacement instances according to your chosen Traffic rerouting and Deployment configuration settings.

    For more information about load balancers for CodeDeploy deployments, see Integrating CodeDeploy with Elastic Load Balancing.

13. In Deployment settings, review the default options for rerouting traffic to the replacement environment, which deployment configuration to use for the deployment, and how instances in the original environment are handled after the deployment.

    If you want to change the settings, continue to the next step. Otherwise, skip to step 15.

14. To change the deployment settings for the blue/green deployment, change any of the following settings.

    Setting	Options
    Traffic rerouting	Reroute traffic immediately: As soon as instances in the replacement environment are provisioned and the latest application revision is installed on them, they are registered with the specified load balancers and target groups automatically, causing traffic to be rerouted to them. Instances in the original environment are then deregistered. I will choose whether to reroute traffic: Instances in the replacement environment are not registered with the specified load balancers and target groups unless you manually reroute traffic. If the wait time you specify passes without traffic being rerouted, the deployment status is changed to Stopped.
    Deployment configuration	Choose the rate at which instances in the replacement environment are registered with the load balancers and target groups, such as one at a time or all at once. Note After traffic is successfully routed to the replacement environment, instances in the original environment are deregistered all at once no matter which deployment configuration was selected. For more information, see Working with deployment configurations in CodeDeploy.
    Original instances	Terminate the original instances in the deployment group: After traffic is rerouted to the replacement environment, the instances that were deregistered from the load balancers and target groups are terminated following the wait period you specify. Keep the original instances in the deployment group running: After traffic is rerouted to the replacement environment, the instances that were deregistered from the load balancers and target groups are kept running.

15. (Optional) In Advanced, configure options you want to include in the deployment, such as Amazon SNS notification triggers, Amazon CloudWatch alarms, or automatic rollbacks.

    For information about specifying advanced options in deployment groups, see Configure advanced options for a deployment group.

16. Choose Create deployment group.

The next step is to prepare a revision to deploy to the application and deployment group. For instructions, see Working with application revisions for CodeDeploy.