Part 2- Amazon EC2 RDS WordPress

Continued from Part 1 – Fast Amazon AWS Optimized WordPress EC2 RDS S3 Manual Cache Gzip Config – Part 1

The next few steps will take us through the roughest part of setting up our WordPress install.

In the last part we launched an AWS Ubuntu 12.10 EBS boot instance. If you got to this part of the tutorial very fast the instance may still be pending. You can check on the instance by visiting EC2 from the AWS management console. Study everything, but careful you don’t click much. Configuring one thing can lead to many things being created such as more EC2 instances, RDS instances, and more. Until you complete this tutorial or have a good grasp on the AWS console, please be careful.


Associate Your Elastic IP, the Dedicated IP

Elastic IP 1From the EC2 console along the left side, choose Elastic IPs. You will first need to click allocate new address. Next you will want to click associate address.

Find the reference to your instance that was launched in the previous tutorial in the drop down menu. After choosing the instance you want to associate you can continue. Completing this step now will make pointing your domain to the server a much more smooth process later. Keep up with Yo.ur.El.ast.ic.IP address. You will need it soon.

Elastic IP 2

Configure Security

Security Setting are next for setting up. We typically start by using the default security group set up during our Ubuntu instance install. The security group during production is set up with minimal security enabled and should be addressed once the site is live.

From the EC2 console, click “Security Groups” along the left side of the screen.

Click on the default, then Choose Inbound



Configure Security GroupWhere labeled “Custom TCP-rule” click the drop down and click SSH. Click add new rule.

The rule should come up with TCP Port 22 (SSH) and source 0.0.0.0/0 to the right.

Repeat for HTTP and mySQL

HTTP will be port 80 and mySQL will be 3306. Make sure you click OK to save the settings. Return back to the Security Group to make sure your settings saved. These are not safe settings and it is recommended that you change them asap, but after you finish this tutorial :)

Launch RDS MySQL Database Instance

Creating the MySQL, Amazon Relational Database Server (RDS) setup with automatic backups (EBS snapshots).

Access RDS ConsoleFrom the AWS Management Console (https://console.aws.amazon.com/) click into “RDS.”

Under the “Database” group or on the main page or wherever Amazon may have the option as you read this, click Launch DB Instance. Select MySQL. Continue to follow on. Set the DB class to micro (t1). CHOOSE NO FOR multi-AZ deployment. Start with the minimum storage unless you know you need more.

MAKE CERTAIN the instance name and master username and password are kept up with. You are going to need them soon. I usually set the DB Instance Identifier and Username to the same, but it is up to you. The security becomes a little much, especially knowing the NSA runs AWS.

Next you will be asked for a database name. Please keep up with this. It will be referred to later as YourDBName from Part 2. It will be your wordpress database, but for the love of WordPress, please don’t name the database wordpress. Make sure your database instance is in the same Zone as your EC2 server instance. Open the AWS Console in another window if you need to find the information.

Make sure default is in the VPC Security Groups drop down.

In management options, accept the backups. Choose a retention period. (I like 21 without any other preferences :)

Complete the wizard, creating the new MySQL RDS.

It typically takes longer for the DB instance to set up than it does for the EC2 Ubuntu instance.

Grab some coffee. B-)

This tutorial has more to come. After the set-up is complete, navigate to the RDS Dashboard and click the line DB Instances. Details about the instance in the lower area include an Endpoint value. This is the database host name you will need later on to connect your WordPress server with the database.

Continue on the Part 3- Configure Your AWS Server

Comments are closed.