Came here to say the same thing - I'd love to see a monthly cost on a setup that looks like this... or anything on AWS. I can run many many WP sites on a $10/month box (not AWS) with proper config tunings.
The smallest production instance on AWS is about $100 a month (c4.large) for 1 core (+intel HT) + 4GB ram + a few GB of EBS volume.
The setup requires at least 4 hosts, thus that's a start price of $400 a month + the other fees (hardly 10% more :D).
It's f* insane to pay more than $400 per month to run a blog. No matter the traffic.
>It's f* insane to pay more than $400 per month to run a blog. No matter the traffic.
Not to mention that guys who can do that kind of custom setup are going for $150-300k a year nowadays. And it's gonna take man*months of work and maintenance.
They are cheap, overrallocated, burstable instances with a low quota of CPU usage (about 10% for a t2.micro). They can burst over the quota for short period of time and they can be interrupted for short period of time.
In short, the instance can pause anytime and stop processing traffic.
Try running a production database on that see where it gets you ;)
There are plenty of production workloads that are burst based in nature, and for those, t2's make plenty of sense. The micro is also hardly the only instance in the family - if you go to the opposite end, the t2.large has a baseline of 60%.
They also are not interrupted or paused, so I don't know where you're getting that. If you run out of credits your performance is throttled to baseline gradually over 15 minutes.
t2s are fine for production if you understand their strengths - workloads with low levels of constant usage and periodic bursts of higher resource utilization.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/t2-instan...