I decided that my foray into AWS needed a dedicated platform, so here it is (aws.802101.com). My original plan was to do a complete lift and shift of www.802101.com, but that did not turn out well, and me, being impatient, decided to start with something a little easier. So, I started afresh with WordPress in AWS. I am using the same template, and the reason for this will be clearer shortly. But let’s have a little look at how easy it is to set up WordPress in AWS.
WordPress in AWS
I have decided to use the free tier WordPress for this, it’s eligible for the free tier as a t2 micro instance (https://aws.amazon.com/free/), which will probably be absolutely fine for this. There is a custom built instance in the EC2 marketplace, just do a search for WordPress and select the Bitnami one at the top:
Review your settings.
Create a key pair (or use an existing one) and launch!
It takes a few moments for the instance to spin up.
Once it’s spun up, you can go to your instances in the dashboard.
Or you can go to your billing details and set some alerts (I would advise that you do this to keep track of any surprise costs).
In the EC2 dashboard, you can get the DNS and IP address and see your running WordPress instance.
There it is, with the default theme.
If you want to SSH into it, you can get the details in the system log (EC2 dashboard > Actions > Instance Settings > Get System Log):
But how does it compare to the platform I am paying for, for the main website?
The main site has had a lot of time spent trying to get it speedy, and gets a fairly good score from the tests:
Google PageSpeed insights:
2 CPU Core
2 GB RAM
30 GB SAN Storage
1 TB Network Bandwidth
I am paying $299.88 per year for this (plus VAT/taxes), and it provides a good benchmark for comparing against running WordPress in AWS.
Google PageSpeed Insights:
The next step will be to look implementing a CDN in the form of CloudFront and an SSL cert.