AWS Bills
Added 2018-12-05 08:29:58 +0000 UTCThought you guys might find it interesting to see what AWS spend looks like. This post is somewhat of a follow up for my previous post about Linode.
During October and November I experimented with moving the Egee.io infrastructure to AWS. You can read more about that journey in this post.
AWS offers a handy DIY DNS service called Route53. Among many other things, it handles DNS and domain registry the same way GoDaddy or Google Domains does.
Route53 is quite a bit cheaper than the other services. For example, registering the Egee.io domain name cost $60 a year with Google Domains. With Route53, it was $40. On the flipside, Route53 is nowhere near as easy to setup as Google Domains.
You can see how I have Egee.io's domain stuff setup in Terraform here. This code literally creates and setups up Egee io domain name and routing. Pretty amazing.
Aside from the Route53 stuff, I also experimented with several EC2 instance types. I had the instances running out of Ohio because it was as close to the central US as AWS offers. Much like Azure, AWS has lots of hidden costs associated with running instances, namely around storage.
For example in November, storage costs accounted for around $7 of my total AWS spend that month, and that wasn't even half a month of overall usage.
One great thing about these bills is that it allows me to itemize the amount of spend out of pocket on running Egee.io"s infrastructure. As of now I'm still running all of our servers on physical hardware in my garage. Hopefully in January we'll be fully switched over to the cloud!
