Alright, so, we’ve set up our EC2 instance, and now we need to set up a database for our EC2 instance to access.
Head back to the console and select the RDS service.
Select the “Launch a DB Instance” button. Follow the Wizard as it makes it super easy to set up. There are a few additional options you should make sure that you choose to avoid extra charges.
I’m used to using WordPress with a mysql db, so I chose the mysql option.
This isn’t really a commercial production site we’re creating and we want the free tier, so select No.
The only changes you should make on the DB Instance Details are:
DB Instance Class: db.t1.micro
Multi-AZ Deployment: No
Allocated Storage: 5 (You can choose up to 5 GB for the free tier) It should be good enough for us.
DB Instance Identifier, Master Username, Master Password – Whatever you put in here, make sure you remember it.
Give your Database a name and choose the vpc and availability zone that you placed your instance in. The reason you want them to be in the availability zone is so that you don’t incur cross AZ fees. Imagine a datacenter, if all the traffic is within a single datacenter we don’t have to pay an outside provider to use their transfer lines, but if you need to cross to a different datacenter, you have to lease a line. This is the same concept.
After this, Review your setup and launch!
Next post will be about setting up an S3 repo.