Does anyone know if these pricing changes are retroactive for customers that have already purchased the reserved instances?
It's pretty much Caveat emptor with them.
91–100 of 151 posts
Does anyone know if these pricing changes are retroactive for customers that have already purchased the reserved instances?
It's pretty much Caveat emptor with them.
I just reserved a series of heavy-utilization m3.xlarge instances for roughly $30k. Apparently, if I had waited a month, I could have saved about $13k because of these price reductions. I can't help but feel that I got really fucked by poor timing that I couldn't control. It would hurt so much less if these price changes were more gradual and somewhat consistent (perhaps monthly).
It's worth calling and talking to your sales rep about this. I've found AWS to be surprisingly accommodating with pricing.
:)
Just out of curiosity, why would one choose AWS over Digital Ocean? Isn't DO considerably cheaper?
Earlier quoted context omitted.
It's worth calling and talking to your sales rep about this. I've found AWS to be surprisingly accommodating with pricing.
I accidentally ran a spot instance for $70 an hour for two hours due to my less-then-smart configuration. They refunded me. :)
Whoops, sounds like bitter (but still good) news for companies like ours that have million-dollar contracts of reserved instances. If we were to grab our reserved instances right now instead of a few months ago, we'd have saved more than half a million over the next year. Bleh.
Earlier quoted context omitted.
That makes sense, thanks for the clarification. Bummer, though. We just reserved a multi-AZ m3.large RDS instance last week. I wish AWS would take up Google's system of graduated price reductions over steady run duration.
The other fun tidbit is on heavy reservations you pay per-hour even if you're not using the machine. That's not the case for the light or medium. So keep that in mind when planning out your reservations. When we switched off EC2 it was financially advantageous to basically give away our heavy instances on the marketplace just to shed the liability.
Whoops, sounds like bitter (but still good) news for companies like ours that have million-dollar contracts of reserved instances. If we were to grab our reserved instances right now instead of a few months ago, we'd have saved more than half a million over the next year. Bleh.
There are a bunch of calculators to compare reserved vs. on demand pricing, but it just occurred to me that they should really be comparing reserved vs. predicted on demand pricing, taking into account inevitable future price drops. Instead of locking in savings, reserved instances are really locking in today's high prices.
Earlier quoted context omitted.
DO is great for hacking on personal projects. I prefer AWS for work stuff because firewall, security groups and networking are much easier to manage. I have not yet tried GCE but I may move some of my dev stuff over once they roll out the private git repos.
The private git repos rolled out a while ago. https://source.developers.google.com/p/PROJECT/r/default You might have to turn it on in your developer console, not sure. At the moment, pushing to its "master" branch tries to deploy to app engine, so that might not be what you're looking for. You can clone it (and, in the future, your connected repos and other Google-hosted repos) with 'gcloud init PROJECT', and things…
ec2 pricing is just a small piece of the whole bill. but it is great to see the price drops, thanks google! wonder if there would be price battle on bandwidth.
how are they still making profits ?