I had been running my WordPress blog on a shared hosting account at hostforweb.com for the last eight years, when about a month ago I decided to consider alternative solutions. In particular, I wanted to see if I can lower the cost of running my site. Here was my starting point:
Web Hosting from hostforweb.com $71.40 / year (paid in 2-year increments)
Domain Registration from namecheap.com $10.87 / year
SSL Certificate from namecheap.com (promotion) $1.99 / year
Given that my blog gets very low traffic, I decided to give AWS a shot. With microbilling, I thought I should be able to drive the cost of my hosting even further down from the already low $6.86/month at hostforweb (for comparison, a blog hosted on wordpress.com costs $8.25/month, billed yearly, and that does not even include google analytics integration, which I can easily add for free to my self-hosted wordpress site).
TL;DR; I was wrong. Hosting on AWS is more expensive with a lower level of reliability, scalability and higher management overhead.
Just the cost of running the t2.micro VM instance is $9.36/month, and that does not include the cost of the RDS instance and the ELB.
I will share the details of my experience in a later post.