Step 1: Launch an Amazon Linux or Red Hat Enterprise Linux Amazon EC2 Instance
To deploy the WordPress application with AWS CodeDeploy, you'll need an Amazon EC2 instance running Amazon Linux or Red Hat Enterprise Linux (RHEL).
Follow the instructions in Working with Instances. When you
get to the part in those instructions about assigning an Amazon EC2 instance tag to the instance,
be sure to specify the tag key of
Name and the tag value of
CodeDeployDemo. (If you specify a different tag key or
tag value, then the instructions in Step 4: Deploy Your
Application may produce unexpected
After you've followed the instructions to launch the Amazon EC2 instance, return to this page, and continue to the next section. Do not continue on to Create an Application as a next step.
Connect to Your Amazon Linux or RHEL Amazon EC2 Instance
After your new Amazon EC2 instance is launched, follow these instructions to practice connecting to it.
Use the ssh command (or an SSH-capable terminal emulator like PuTTY) to connect to your Amazon Linux or RHEL Amazon EC2 instance. You will need the public DNS address of the instance and the private key for the key pair you used when you started the Amazon EC2 instance. For more information, see Connect to Your Instance.
For example, if the public DNS address is
ec2-01-234-567-890.compute-1.amazonaws.com, and your Amazon EC2 instance key pair for SSH access is named
codedeploydemo.pem, you would type:Copy
with the path to your
.pemfile and the example DNS address with the address to your Amazon Linux or RHEL Amazon EC2 instance.
If you receive an error about your key file's permissions being too open, you will need to restrict its permissions to give access only to the current user (you). For example, with the chmod command on Linux, macOS, or Unix, type:Copy
After you are signed in, you will see the AMI banner for the Amazon EC2 instance. For Amazon Linux, it should look like this:Copy
__| __|_ ) _| ( / Amazon Linux AMI ___|\___|___|
You can now sign out of the running Amazon EC2 instance.
Do not stop or terminate the Amazon EC2 instance. Otherwise, AWS CodeDeploy won't be able to deploy to it.