AWS Reserved Instances optimization - configure a report
Teevity can provide a detailed report about how much money you can save by committing to buy EC2 Reserved Instances. This page provides steps to configure an AWS Reserved Instance Optimization report. You will find more details about how to read a RI Optimization report on here.
Enable the Reserved Instance Optimization feature
Please contact the support team at firstname.lastname@example.org
Select a Cost Partition used for the Reserved Instances Optimization report
To get the most of the report it's important to choose the right window on your EC2 instances and so in Teevity this is done by selecting a cost partition for which you will get the optimization information.
Go to the cost allocation units section of the Preferences pages and select the cost partition (1) used for the optimisation report:
When a cost partition is selected, by default its cost allocation units are selected as candidate for long term commitment. You can change this on a cost allocation unit basis:
Add the Reserved Instances Optimization report to your dashboard
As you would do for any other report, go to your dashboard and select the checkbox "Show all Reports" (1) and then you should see a report called "RI recommendations for ..." (2).
Configuration of the report results
When you consult the details of a report, you will have the opportunity to change (1) the parameters of the recommandations algorithm:
- the button to show or hide the panel with the parameters
- AWS offers different types of RI and commitment terms which have an impact on the savings (more details on the AWS documentation website)
- As we have described above, the cost partition on which the savings are based
- If you want to put a maximum amount on the commitment
- See below
- As we have also described above, you can choose to include only the cost allocation units which are tagged as "long term commitment" but you can also select specific tags based on a filter
This options lets configure how the optimization of Reserved Instances are going to be affected by the tags selected.
Imagine an application "A" for which the instances are used only during the normal office hours. It would not make sense to buy RIs for it since the usage level will be too low (40 hours on a week of 168 hours i.e. 23%).
But if you have another application "B" for which the instances are of the same type as application A and used during 8 hours during the night time or another time zone then it would make sense to commit since the combined usage is higher than the breakeven threshold (which depends of your commitment terms see set (2)).
The option (5) lets you decide to include or not Reserved Instances which would become "in the money" if we take into consideration other potential usage filter out by the tag(s) selected.