We’ve split out upfront charges for Reserved Instances/Capacity as separate AWS services in Stax. This has been done for EC2, RDS, Redshift (Reserved Instances) and Dynamo (Reserved Capacity).
This has two effects in Stax:
- You can now see RI’s as a separate line item when you drill down to the service level in Total Cost & Raw Data. This makes it clearer when a spike in cost is due to a Reserved Instance purchase or charge; vs when it’s due to usage of those services.
- Upfront RI costs can now be allocated across your organisation using Cost Allocation rules, setup on the Settings page. You can choose to allocate upfront RI costs to one cost category only; or to many using the Shared Costs table.
Which upfront Reserved Instance/Capacity charges are included?
Upfront charges & recurring payments for Reserved Instances for EC2, RDS, Redshift and Reserved Capacity for Dynamo are all split out as separate line items.
How can I allocate upfront RI charges across multiple categories?
- In the Shared Cost table, define a shared cost type, e.g. “RI EC2” and allocate the percentages to each cost category that share this cost. Click ‘Add’
- Create a rule in the Cost Allocation table to allocate RI – EC2 charges to that shared cost item. Select “RI EC2” in the first column; and select “RI – EC2” in the Product Column. Click “Add” to add the rule to the table. That rule will allocate upfront RI EC2 costs across your cost categories as per the percentages entered in the Shared Cost table above.
What about no upfront or partial upfront RIs?
There is an hourly cost associated with these payment types, which will default to being charged to the account that those RIs were purchased from. If you want to allocate those costs to categories outside of those accounts, you need to ensure the rule sits above any rules that capture all costs in those accounts in the Cost Allocation Rules table.