Love the idea and implementation, thanks a lot for this!
Though more granularity, as it has been said, would be nice, this is good enough for me and lots of people as it is right now.
What I REALLY would like to see (and I know this is not really a feature request for this, but just an idea I'm throwing out there) is this made for other Amazon AWS services as well.
Common scenarios, like "I would like to run a wordpress site on an EC2 instance serving a couple thousand hits per month", or "I'd like to store a 1 TB backup of my personal computer on Glacier and retrieve it when my computer crashes (say in 1 year)".
The point is, like you said yourself, if you're spending a lot of money, you shouldn't trust anyone else, but having these "ballpark figures" would be really useful for people that are considering these services.
To that point, it's hard to get a handle on how many GET, LIST, POST, etc. operations one would routinely do in the course of a blog or something else. While that can get pretty complex (especially if you end up throwing varnish in to minimize calls to your datastore), a calculator including various rules of thumb would be great.
Though more granularity, as it has been said, would be nice, this is good enough for me and lots of people as it is right now.
What I REALLY would like to see (and I know this is not really a feature request for this, but just an idea I'm throwing out there) is this made for other Amazon AWS services as well.
Common scenarios, like "I would like to run a wordpress site on an EC2 instance serving a couple thousand hits per month", or "I'd like to store a 1 TB backup of my personal computer on Glacier and retrieve it when my computer crashes (say in 1 year)".
The point is, like you said yourself, if you're spending a lot of money, you shouldn't trust anyone else, but having these "ballpark figures" would be really useful for people that are considering these services.