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

Step 5: Try the AWS CodeDeploy Sample Deployment Wizard

After you have completed the first four steps in Getting Started, try the Sample deployment wizard. It guides you through the steps for creating an AWS CodeDeploy deployment. The Sample deployment wizard lets you try an in-place deployment and a blue/green deployment.

In-place deployment: Instances in a deployment group are taken offline (with or without the use of a load balancer in Elastic Load Balancing), updated with the latest application revision, and then placed back online as part of the same deployment group. For more information about in-place deployments, see Overview of an In-Place Deployment.

Blue/green deployment: The instances in a deployment group (the original environment) are replaced by a different set of instances (the replacement environment) using these steps:

  • Instances are provisioned for the replacement environment.

  • The latest application revision is installed on the replacement instances.

  • An optional wait time occurs for activities such as application testing and system verification.

  • Instances in the replacement environment are registered with an Elastic Load Balancing load balancer, causing traffic to be rerouted to them. Instances in the original environment are deregistered and can be terminated or kept running for other uses.

For more information about blue/green deployments, see Overview of a Blue/Green Deployment.

For both deployment type samples, we assume you have no prior experience with AWS CodeDeploy and have not yet created any resources, such as applications, application revisions, or deployment groups in AWS CodeDeploy.

These topics refer to resources and concepts that are unique to AWS CodeDeploy. To familiarize yourself with them before you start, see Primary Resources.


If you want AWS CodeDeploy to create some sample Amazon EC2 instances, you must have an Amazon EC2 instance key pair. To create an Amazon EC2 instance key pair, follow the instructions in Creating Your Key Pair Using Amazon EC2. Be sure your Amazon EC2 instance key pair is created in one of the regions listed in Region and Endpoints in the AWS General Reference. You must create an Amazon EC2 instance key pair before you start the wizard. Otherwise, it will not appear in the Key pair name drop-down list in the Sample deployment wizard.

If you use the AWS CloudFormation template to launch Amazon EC2 instances, the calling IAM user must have access to AWS CloudFormation and AWS services and actions on which AWS CloudFormation depends. If you have not followed the steps in Step 1: Provision an IAM User to provision the calling IAM user, you must at least attach the following policy:

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "cloudformation:*", "codedeploy:*", "ec2:*", "iam:AddRoleToInstanceProfile", "iam:CreateInstanceProfile", "iam:CreateRole", "iam:DeleteInstanceProfile", "iam:DeleteRole", "iam:DeleteRolePolicy", "iam:GetRole", "iam:PassRole", "iam:PutRolePolicy", "iam:RemoveRoleFromInstanceProfile" ], "Resource": "*" } ] }

The following portion of the policy grants the calling IAM user access to the IAM actions required to create the service role.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "iam:CreateRole", "iam:PutRolePolicy" ], "Resource": "*" } ] }

The following portion of the policy grants the calling IAM user permission to create applications and deployment groups and deploy applications.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "codedeploy:*" ], "Resource": "*" } ] }

On this page: