3 ms·
I can't speak for the other regions but in ap-southeast-2 we had a couple of incidents in 2019 where there was no Spot capacity for ANY instance types between s
by threeseed 7y ago
I can't speak for the other regions but in ap-southeast-2 we had a couple of incidents in 2019 where there was no Spot capacity for ANY instance types between say 64GB and 512GB of RAM.
And so even our instance fleets were failing to provision capacity.
- tuananh 7y agothis is why ability to fall back to on-demand instances is critical.
- paulddraper 7y agoIt seems weird that AWS wouldn't just do this automatically, right?
- llarsson 7y agoYes and no. Because they do not want to disclose how much capacity they have and on demand costs more, customers would be left wondering if AWS unfairly decided to run on demand when spot could have been used instead.
- londons_explore 7y agoWhen there are no spot instances, it's common that on-demand instances can't be started either. Unless you paid for a reservation, you're SOL.
- tuananh 7y agothat's for you to decide how many percent of reserved instances out of total compute power you need. it's always a trade off. in that case, pct of cost saving is lower but availability is higher.
- maniktan 7y agoFwiw, Product@SpotInst here. Curious what makes you arrive at this conclusion? At SpotInst we have customers who migrate between Spot <--> RI <--> OD everyday.
- ramraj07 7y agoRequiring a minimum of 64GB RAM seems quite unique computationally, so if it's mission critical that you have at least one instance of this type all the time up, then maybe you could reserve that one instance fully while depending on spots for scaling?