Create an Amazon EC2 instance for CodeDeploy (Amazon CLI or Amazon EC2 console) - 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 (PDF).

Create an Amazon EC2 instance for CodeDeploy (Amazon CLI or Amazon EC2 console)

These instructions show you how to launch a new Amazon EC2 instance that is configured for use in CodeDeploy deployments.

You can use our Amazon CloudFormation template to launch an Amazon EC2 instance running Amazon Linux or Windows Server that is already configured for use in CodeDeploy deployments. We do not provide an Amazon CloudFormation template for Amazon EC2 instances running Ubuntu Server or Red Hat Enterprise Linux (RHEL). For alternatives to the use of the template, see Working with instances for CodeDeploy.

You can use the Amazon EC2 console, Amazon CLI, or Amazon EC2 APIs to launch an Amazon EC2 instance.

Launch an Amazon EC2 instance (console)

Prerequisites

If you have not done so already, follow the instructions in Getting started with CodeDeploy to set up and configure the Amazon CLI and create an IAM instance profile.

Launch an Amazon EC2 instance

  1. Sign in to the Amazon Web Services Management Console and open the Amazon EC2 console at https://console.amazonaws.cn/ec2/.

  2. In the navigation pane, choose Instances, and then choose Launch Instance.

  3. On the Step 1: Choose an Amazon Machine Image (AMI) page, from the Quick Start tab, locate the operating system and version you want to use, and then choose Select. You must choose an Amazon EC2 AMI operating systems supported by CodeDeploy. For more information, see Operating systems supported by the CodeDeploy agent.

  4. On the Step 2: Choose an Instance Type page, choose any available Amazon EC2 instance type, and then choose Next: Configure Instance Details.

  5. On the Step 3: Configure Instance Details page, in the IAM role list, choose the IAM instance role you created in Step 4: Create an IAM instance profile for your Amazon EC2 instances. If you used the suggested role name, then choose CodeDeployDemo-EC2-Instance-Profile. If you created your own role name, choose that.

    Note

    If a default virtual private cloud (VPC) is not displayed in the Network list, you must choose or create an Amazon VPC and subnet. Choose Create new VPC or Create new subnet or both. For more information, see Your VPC and subnets.

  6. Choose Next: Add Storage.

  7. Leave the Step 4: Add Storage page unchanged, and choose Next: Add Tags.

  8. On the Step 5: Add Tags page, choose Add Tag.

  9. In the Key box, type Name. In the Value box type CodeDeployDemo.

    Important

    The contents of the Key and Value boxes are case-sensitive.

  10. Choose Next: Configure Security Group.

  11. On the Step 6: Configure Security Group page, leave the Create a new security group option selected.

    A default SSH role is configured for Amazon EC2 instances running Amazon Linux, Ubuntu Server, or RHEL. A default RDP role is configured for Amazon EC2 instances running Windows Server.

  12. If you want to open the HTTP port, choose the Add Rule button, and from the Type drop-down list, choose HTTP. Accept the default Source value of Custom 0.0.0.0/0, and then choose Review and Launch.

    Note

    In a production environment, we recommend restricting access to the SSH, RDP, and HTTP ports, instead of specifying Anywhere 0.0.0.0/0. CodeDeploy does not require unrestricted port access and does not require HTTP access. For more information, see Tips for securing your Amazon EC2 instance.

    If a Boot from General Purpose (SSD) dialog box appears, follow the instructions, and then choose Next.

  13. Leave the Step 7: Review Instance Launch page unchanged, and choose Launch.

  14. In the Select an existing key pair or create a new key pair dialog box, choose either Choose an existing key pair or Create a new key pair. If you've already configured an Amazon EC2 instance key pair, you can choose it here.

    If you don't already have an Amazon EC2 instance key pair, choose Create a new key pair and give it a recognizable name. Choose Download Key Pair to download the Amazon EC2 instance key pair to your computer.

    Important

    You must have a key pair if you want to access your Amazon EC2 instance with SSH or RDP.

  15. Choose Launch Instances.

  16. Choose the ID for your Amazon EC2 instance. Do not continue until the instance has been launched and passed all checks.

Install the CodeDeploy agent

The CodeDeploy agent must be installed on your Amazon EC2 instance before using it in CodeDeploy deployments. For more information, see Install the CodeDeploy agent.

Note

You can configure automatic installation and updates of the CodeDeploy agent when you create your deployment group in the console.

Launch an Amazon EC2 instance (CLI)

Prerequisites

If you have not done so already, follow the instructions in Getting started with CodeDeploy to set up and configure the Amazon CLI and create an IAM instance profile.

Launch an Amazon EC2 instance

  1. For Windows Server only If you are creating an Amazon EC2 instance running Windows Server, call the create-security-group and authorize-security-group-ingress commands to create a security group that allows RDP access (which is not allowed by default) and, alternatively, HTTP access. For example, to create a security group named CodeDeployDemo-Windows-Security-Group, run the following commands, one at a time:

    aws ec2 create-security-group --group-name CodeDeployDemo-Windows-Security-Group --description "For launching Windows Server images for use with CodeDeploy"
    aws ec2 authorize-security-group-ingress --group-name CodeDeployDemo-Windows-Security-Group --to-port 3389 --ip-protocol tcp --cidr-ip 0.0.0.0/0 --from-port 3389
    aws ec2 authorize-security-group-ingress --group-name CodeDeployDemo-Windows-Security-Group --to-port 80 --ip-protocol tcp --cidr-ip 0.0.0.0/0 --from-port 80
    Note

    For demonstration purposes, these commands create a security group that allows unrestricted access for RDP through port 3389 and, alternatively, HTTP through port 80. As a best practice, we recommend restricting access to the RDP and HTTP ports. CodeDeploy does not require unrestricted port access and does not require HTTP access. For more information, see Tips for securing your Amazon EC2 instance.

  2. Call the run-instances command to create and launch the Amazon EC2 instance.

    Before you call this command, you need to collect the following:

    • The ID of an Amazon Machine Image (AMI) (ami-id) you use for the instance. To get the ID, see Finding a suitable AMI.

    • The name of the type of Amazon EC2 instance (instance-type) you create, such as t1.micro. For a list, see Amazon EC2 instance types.

    • The name of an IAM instance profile with permission to access the Amazon S3 bucket where the CodeDeploy agent installation files for your region are stored.

      For information about creating an IAM instance profile, see Step 4: Create an IAM instance profile for your Amazon EC2 instances.

    • The name of an Amazon EC2 instance key pair (key-name) to enable SSH access to an Amazon EC2 instance running Amazon Linux, Ubuntu Server, or RHEL or RDP access to an Amazon EC2 instance running Windows Server.

      Important

      Type the key pair name only, not the key pair file extension. For example, my-keypair, not my-keypair.pem.

      To find a key pair name, open the Amazon EC2 console at https://console.amazonaws.cn/ec2. In the navigation pane, under Network & Security, choose Key Pairs, and note the key pair name in the list.

      To generate a key pair, see Creating your key pair using Amazon EC2. Be sure you create the key pair in one of the regions listed in Region and endpoints in Amazon Web Services General Reference. Otherwise, you won't be able to use the Amazon EC2 instance key pair with CodeDeploy.

    For Amazon Linux, RHEL, and Ubuntu Server

    To call the run-instances command to launch an Amazon EC2 instance running Amazon Linux, Ubuntu Server, or RHEL and attach the IAM instance profile you created in Step 4: Create an IAM instance profile for your Amazon EC2 instances. For example:

    aws ec2 run-instances \ --image-id ami-id \ --key-name key-name \ --count 1 \ --instance-type instance-type \ --iam-instance-profile Name=iam-instance-profile
    Note

    This command creates a default security group for the Amazon EC2 instance that allows access to several ports, including unrestricted access for SSH through port 22 and, alternatively, HTTP through port 80. As a best practice, we recommend restricting access to the SSH and HTTP ports only. CodeDeploy does not require unrestricted port access and does not require HTTP port access. For more information, see Tips for securing your Amazon EC2 instance.

    For Windows Server

    To call the run-instances command to launch an Amazon EC2 instance running Windows Server and attach the IAM instance profile you created in Step 4: Create an IAM instance profile for your Amazon EC2 instances, and specify the name of the security group you created in Step 1. For example:

    aws ec2 run-instances --image-id ami-id --key-name key-name --count 1 --instance-type instance-type --iam-instance-profile Name=iam-instance-profile --security-groups CodeDeploy-Windows-Security-Group

    These commands launch a single Amazon EC2 instance with the specified AMI, key pair, and instance type, with the specified IAM instance profile, and run the specified script during launch.

  3. Note the value of the InstanceID in the output. If you forget this value, you can get it later by calling the describe-instances command against the Amazon EC2 instance key pair.

    aws ec2 describe-instances --filters "Name=key-name,Values=keyName" --query "Reservations[*].Instances[*].[InstanceId]" --output text

    Use the instance ID to call the create-tags command, which tags the Amazon EC2 instance so that CodeDeploy can find it later during a deployment. In the following example, the tag is named CodeDeployDemo, but you can specify any Amazon EC2 instance tag you want.

    aws ec2 create-tags --resources instance-id --tags Key=Name,Value=CodeDeployDemo

    You can apply multiple tags to an instance at the same time. For example:

    aws ec2 create-tags --resources instance-id --tags Key=Name,Value=testInstance Key=Region,Value=West Key=Environment,Value=Beta

    To verify the Amazon EC2 instance has been launched and passed all checks, use the instance ID to call the describe-instance-status command.

    aws ec2 describe-instance-status --instance-ids instance-id --query "InstanceStatuses[*].InstanceStatus.[Status]" --output text

If the instance has been launched and passed all checks, ok appears in the output.

Install the CodeDeploy agent

The CodeDeploy agent must be installed on your Amazon EC2 instance before using it in CodeDeploy deployments. For more information, see Install the CodeDeploy agent.

Note

You can configure automatic installation and updates of the CodeDeploy agent when you create your deployment group in the console.