[deleted]
AWS Costs Cheat Sheet
11–20 of 37 posts
Re: AWS Costs Cheat Sheet
#12Aren't the on-demand prices a bit useless? Doesn't everyone reserve instances?
Depends very much what you're using it for. I do a lot of ad-hoc data processing and use on-demand all the time.
Re: AWS Costs Cheat Sheet
#13my mini-comparison Cloud Static Storage (cents/gigabyte) site storage bandwidth dreamobjects 7 7 http://dreamhost.com/cloud/dreamobjects/pricing/ cloudfiles 10 18 http://www.rackspace.com/cloud/public/files/pricing/ amazon s3 12.5 12 http://aws.amazon.com/s3/pricing/
What about performance?
And reliability.
S3 is specced as being very reliable.
Re: AWS Costs Cheat Sheet
#14Complementary chart:
Re: AWS Costs Cheat Sheet
#15This is very useful. Spot instance costs would be really doubly useful, particularly if you can put them alongside on-demand costs.
Spot instance prices change hourly, so they probably don't make sense to add to a static list like this.
Yep, I understand that. Still, spot pricing it relatively consistent over time, with occasional temporary spikes. A dynamic web version with this format would work too. It's less important to me that I can print it out, since I probably would just end up referring to this online as I need it.
Re: AWS Costs Cheat Sheet
#16Very cool! This is useful for small deployments. We developed PlanForCloud.com to help with cost forecasting for big deployments, where you want to compare infrastructure options and cloud providers.
Also, don't forget that one of the key benefit of using the cloud is elasticity, and unless you model this, you won't get accurate estimates. We developed the notion of elasticity patterns[1] to let users do this, so you can say something like "my baseline S3 storage is 100GB, but every month this grows by 5% and in the Christmas it doubles".
Re: AWS Costs Cheat Sheet
#17Finally a summary I can use.
Re: AWS Costs Cheat Sheet
#18I'd really love to jump on EC2, but every time I run the numbers it doesn't add up for my usage.
I currently colocate all my servers and I wanted to figure out just how much it might cost to potentially switch over to EC2. After much digging and benchmarking, it seems that an single ECU is roughly equivalent to 350 to 400 points on PassMark. With this information and load metrics, it is pretty easy to determine what kind of ECUs I might need to switch over (as RAM and disk are pretty straight forward): http://www.cpubenchmark.net/cpu_list.php.
Came to the same conclusion as I did a few years ago. For my scenario (about a rack of servers, established business, 24/7 usage, capacity to handle for a 10-fold increase in usage (and much more within a 2 hour window))... I save roughly $170,000 over 3 years doing it all (server costs included). This is with 3-year reserved instances.
It should be noted that I build our servers from the ground up and do all the ops.
Re: AWS Costs Cheat Sheet
#19Complementary chart: http://www.ec2instances.info/
Having built a SaaS app that basically means spinning up a new instance for each customer, I reference ec2instances.info almost daily.
I only came into this discussion to post it -- glad to see somebody else already did.
Re: AWS Costs Cheat Sheet
#20I'd really love to jump on EC2, but every time I run the numbers it doesn't add up for my usage. I currently colocate all my servers and I wanted to figure out just how much it might cost to potentially switch over to EC2. After much digging and benchmarking, it seems that an single ECU is roughly equivalent to 350 to 400 points on PassMark. With this information and load metrics, it is pretty easy to determine what…
If you include how much your salary, bonuses, equity and health care costs the business, does it change your calculations?