Why Switching to AWS May Cost You A Fortune

Every month we lose a couple of customers to Amazon's Cloud or AWS (Amazon Web Services) and every month we have another couple of customers sign up with us having just cancelled their AWS solution.  Each time their reasoning for leaving AWS is the same, “way more expensive and way less performance than we expected, especially when compared to what we get from a dedicated server”.  This conversation has come up so frequently we thought it was worth doing a little analysis to find out exactly what these folks are talking about.

It only took me about 30 seconds with the AWS EC2 price calculator to figure out where that “way more expensive” issue might be coming fromv in the AWS cost.  Before I dive into my findings, let me give you a quick history on the evolution of bandwidth pricing on bare-metal servers.

Over last few years the amount of bandwidth included with a dedicated server has increased industry wide.   A decade ago it was common for an entry-level server to include 1000GB (gigabyte) of monthly data transfer, then it was 2000, then 3000.   Today you will now find most bare-metal hosting providers including anywhere from 5TB to 20TB with every server they offer…and a lot of times that is on a 1Gbps (gigabits per second) port.  The data center and hosting industry has consistently increased the included server bandwidth for a couple of reasons.  First, the usage of the worldwide web increases every day…every hour really.  With that increased usage comes more content, more streaming, more videos and just much more data flowing across the web.  Our average customer was fine with 1000GB of bandwidth 10 years ago, heck they were fine with 500GB, but today our average customers are transferring thousands of gigabytes every month and bursting well over 100Mbps (megabits per second).  Secondly, the price of transit i.e. bandwidth, has come down drastically.  Because of the increased bandwidth usage just described, hosting providers are now able to bite off huge commitments with network providers like Level 3, Verizon and Comcast.  The more network throughput a data center commits to each month, the lower the price per Mbps from the carriers.  Additionally, the base price, even on a small 1Gbps commit with these network providers has come down from $15-$30 per Mbps back in 2005 to below $5 per Mbps, and when you get into 10Gbps+ commits, pricing can be driven down to below $1 per Mbps.  So supply and demand has led to more for less, resulting in a better price and experience for the end user. 

Now back to the AWS EC2 price calculator for an estimated AWS cost. One of the very first things you are able to enter is the amount of inbound and outbound AWS bandwidth required.  I started with what I thought was a pretty modest amount of usage, 3000GB out and 300GB in, or the equivalent of just 10Mbps sustained throughout a month.  The cost for this bandwidth, before any compute, backup, IPs or anything else added is $268/month.  I then began incrementally adding more AWS bandwidth in nominal chunks  and below is a breakdown of what I found.

  • 3000GB outbound, 300GB inbound (10Mbps)- $268/month
  • 9000GB outbound, 1000GB inbound (30Mbps)- $808/month
  • 15,000GB outbound, 1500GB inbound (50Mbps)- $1457/month
  • 30,000GB outbound, 3000GB inbound (100Mbps)- $2859/month (shown in screenshot above)
  • 15,0000GB outbound, 15000GB inbound (500Mbps)- $12,410/month

Keep in mind, an entry-level single-tenant guaranteed resource dedicated server typically includes a Quad-Core Xeon CPU with 8GB RAM, 500GB Hdd and most importantly 10TB bandwidth (10,000GB or just over 30Mbps sustained) and costs about $99- $199 per month.  The bottom line is, if your online presence requires 10TB of bandwidth or more, you will likely spend at least $600 more every month ($7000 more per year) than you would with a dedicated server and potentially experience worse performance.  With some providers targeting high-bandwidth users, us included, it is not uncommon to find servers for $200-$600 per month that include 500Mbps or 1Gbps unmetered bandwidth.  The cost comparison under this scenario is even more staggering.  Again, the costs I produced from the EC2 price calculator are before any actual compute or storage capacity was considered.   

Another option is Amazon’s CloudFront CDN solution.  Since a CDN is predicated on high bandwidth usage I had assumed the pricing here would close the gap with bare-metal.  While the price was lower it was still far higher than the costs associated with a dedicated server.   For this evaluation I stuck with only distributing my content within the US to keep things simple.   Keep in the mind, the pricing below does not include the additional cost of $.02 per GB for linking your source server to the CDN or the just under a penny cost for each HTTP and HTTPS request to your content.  Every 10,000 pennies is another $100.

  • 10TB (10,000GB) of CDN bandwidth-$850/ month
  • 20TB of CDN bandwidth- $1650/ month
  • 50TB of CDN bandwidth- $4050/ month
  • 100TB of CDN bandwidth- $7050/month

In summary, it is clear that AWS has its benefits, hence the $5 billion in estimated revenue it will produce this year.  However, if you are a heavy user, or even a moderate user of bandwidth for that matter, it seems to me it will cost you a considerable amount of money every month within the AWS cloud.  To give you some perspective of how this pricing structure would affect some of our dedicated server customers; we just turned up 20 Linux Quad-Core Xeon (with hyper threading) servers last week for 1 customer.  Each server today is pushing about 650Mbps of bandwidth at a cost of just over $600 per month per server.  This one customer is saving an estimated $290,000 every month when compared to AWS.  Now this is likely an extreme example of how a dedicated server can save when compared to Amazon but even a few hundred dollars every month is often a big deal to a small or medium sized company, which just so happens to describe the majority of companies out there.