4 ms·
We made the mistake of buying a ton of reserved instances up front which we have been stuck with because we moved on to a different instance with the high IO.
by sum1randum 14y ago
We made the mistake of buying a ton of reserved instances up front which we have been stuck with because we moved on to a different instance with the high IO. We have been complaining to them about the need for a RI secondary market at all the AWS events we could attend
- simpleenigma 14y agoThis has been my hesitation for doing any reserved instances. I expect to need larger instances in teh next 6 to 12 months, so any reserved instances I purchase today would have extra time on them without utilization ... This at least gives a way to ease the pain of reserving instances that you know you will out grow ...
- tedchs 14y agoHi sum1randum, Have you tried engaging the AWS customer service team on this? AWS has a public face that looks 100% robotic and automated, but I assure you there are AMAZING support & engineering teams behind the scenes who have a strong vested interest to make sure customers are successful using AWS. IMHO, it might be worth a shot to send them a ticket that basically says, we bought RI's for the instance type we needed at the time, but now you guys released the new High IO type, and for us to be successful we really need to upgrade these RI's. So, the ideal outcome is you go buy your new reservations and then they give a prorated credit for the rest of your RI term on the old ones. I would imagine they might still steer you to the RI marketplace now but it's worth a shot if you can be persuasive enough.