Using FlexReports to locate where Unused "SavingsPlanRecurringFee" floated

Products

• CloudHealth

Issue/Introduction

The account totals in CH not matching that of AWS platform can be a combination of two reasons:

1. CloudHealth displays the net costs after EDP discounts are applied while the AWS bill provided by a customer may not. 
2. The difference in how Reserved Instance (RI) coverage and Savings Plans (SPs) are reported in the two systems. CloudHealth reports using actual reservation usage metrics (accounting for RI and SPs float across accounts) while AWS generally keeps reservation cost associated to the accounts that purchased them.

 
Follow the steps in the example below to track where Unused SavingsPlanRecurringFee float to cover usage in other accounts.

Resolution

Using the AWS bill total, you can work your way to match the CloudHealth total.  In the example below, sample AccountId 4###### during Dec-2021 will be used:

 

Calculate the difference between AWS bill and CH bill:

1. AWS total bill - EDP discount (If EDP is not applied to AWS bill already) = $X
2. CH total bill is net cost after EDP applied = $Y
3. The difference = AWS total bill - CH total bill = $Z

 
Explain the difference

1. AWS bill line item "SavingsPlanRecurringFee" = $A
2. CH bill line item "Savings Plans Unused" = $B 
   1. Found under Indirect Charges in Cost History Report
   2. Note: If $B>0, partial SPs usage. If $B=0, SPs usage is 100% and the remaining usage is billed at the On-Demand pricing.
3. The total "Savings Plans Used Commitment" by all accounts during Dec-2021 = $A - $B = $C
4. "Savings Plans Used Commitment" utilized by AccountId 4###### alone = $D
   1. Found under Compute Cost ($) Reports / Usage / Instance / Savings
5. "Savings Plans Used Commitment" utilized by other accounts = $C - $D = $Z (Matches the difference between AWS bill and CH bill)

FlexReports in CloudHealth allows you to drill down further into which accounts the remaining $Z SPs floated to.

1. Go to Reports>FlexReports>create New Report with following Measures, Dimensions and Filters:
2. The table below will populate:
   1. Row in red, UnblendedCost = SavingPlan_UsedCommitment, means SP usage is 100% by account 4######. 
   2. Row in blue, UnblendedCost > SavingPlan_UsedCommitment, means Partial SP usage by account 4###### and the remaining unused SPs floats to usage by other accounts can be tracked by SavingPlanARN. Copy ARN and go to next step.
3. Use SavingPlanARN to locate floating SPs 
   1. In Filters, paste the SavingPlanARN from blue row above and click APPLY.
   2. Remove (UsageAccountID contains 4#######) from filters.
   3. Add Measures > SavingsPlan/SavingsPlanEffectiveCost to obtain the table below:
   4. Observe that account 7##### used $160.38 out of the $1,932.03 SPs UsedCommitment for account 4######. 
   5. Repeat steps above for different SavinsPlanARN to locate SP usage across other accounts.