Decoding AWS Reserved Instances
blog.symops.com
Decoding AWS Reserved Instances
1–10 of 25 posts
Re: Decoding AWS Reserved Instances
#2I think I know what you mean, but this reads like Reserved Instances earn AWS $100 billion/year which is almost impossible. I don't even think AWS earns that much annually.
Re: Decoding AWS Reserved Instances
#3NB they would never call it a lease or rental because those terms have legal repercussions in some jurisdictions.
A reserved instance is simply pre-paying for a specific amount of EC2. AWS is able to discount this because: 1. You're pre-paying 2. You might not use all the resources you're entitled to, if you don't keep a running EC2 instance "filling" the reserved instance slot. 3. You're helping them with capacity planning and capacity management; there's no guesswork involved with your workload.
Re: Decoding AWS Reserved Instances
#4TLDR if you are choosing RI's over Saving Plans the basic info conveyed in this article is probably already know if you don't you should probably just be choosing saving plans.
Re: Decoding AWS Reserved Instances
#5https://docs.vantage.sh/autopilot/ has many details on how our RI management program works. We recently added Autopilot Controls which lets you specify categories of instances (like c5) or regions that you want managed.
One note on buybacks: they are usually capped. I believe most providers cap their "guarantee" around $20K.
Re: Decoding AWS Reserved Instances
#6It probably would have been better if AWS had called them "reservations" rather than "reserved instances". NB they would never call it a lease or rental because those terms have legal repercussions in some jurisdictions. A reserved instance is simply pre-paying for a specific amount of EC2. AWS is able to discount this because: 1. You're pre-paying 2. You might not use all the resources you're entitled to, if you don…
We got to go second, but I prefer the naming and separation of concerns we came up with (obviously): Reservations are capacity you're holding, while Commitments are things that get you discounts.
Reservations are things your operations team uses to guarantee capacity for scaling up, doing rolling restarts, and whatever else. Commitments (and Committed Use Discounts) are primarily what your Finance teams work with.
The original Reserved Instance product combined both of these. AWS now has the same decoupling with Savings Plans and Reservations as related, separate products.
Re: Decoding AWS Reserved Instances
#7Cool to see Vantage mentioned here! I work for them, mainly on the ec2instances.info site. https://docs.vantage.sh/autopilot/ has many details on how our RI management program works. We recently added Autopilot Controls which lets you specify categories of instances (like c5) or regions that you want managed. One note on buybacks: they are usually capped. I believe most providers cap their "guarantee" around $20K.
Re: Decoding AWS Reserved Instances
#8A lot of human hours go into managing them, buying them, selling them, making sure they are efficiently used, etc.
I do wonder if the human effort invested in such things is actually a net gain over a fixed price. Clearly there is gain for the companies using RI's, but is there gain for the economy as a whole?
Re: Decoding AWS Reserved Instances
#9Reserved instances are effectively a financial construct. A lot of human hours go into managing them, buying them, selling them, making sure they are efficiently used, etc. I do wonder if the human effort invested in such things is actually a net gain over a fixed price. Clearly there is gain for the companies using RI's, but is there gain for the economy as a whole?
Almost true. It's also a powerful lock-in mechanism.