CloudHealth New Experience - Classic Savings report vs Commitment Savings section
search cancel

CloudHealth New Experience - Classic Savings report vs Commitment Savings section

book

Article ID: 414285

calendar_today

Updated On:

Products

CloudHealth

Issue/Introduction

Currently when you compare the Classic Savings Report to the Commitment Savings section you may note that the two return different Saving values when comparing:

  • Classic Savings Report's - EC2 Savings from SPs dimension, to the Commitment Savings - Spend based Commitment Savings dimension

  • Classic Savings Reports - EC2 Savings from RIs dimension, to the Commitment Savings - Resource based Commitment Savings dimension

 

Resolution

The difference is due to the Classic Savings report only considering EC2 instances whereas the Commitment Savings section considers all resources that can be utilized via Savings Plan or Reservation. 

The following FlexReport can be used to validate the figures between the two reports -

{
  "sqlStatement": "SELECT SUM(lineItem_UnblendedCost) AS SUM_lineItem_UnblendedCost, SUM(savingsPlan_SavingsPlanEffectiveCost) AS SUM_savingsPlan_SavingsPlanEffectiveCost, timeInterval_Month AS Month, lineItem_LineItemType AS LineItem_LineItemType, SUM(reservation_EffectiveCost) AS SUM_reservation_EffectiveCost, lineItem_ProductCode AS LineItem_ProductCode FROM AWS_CUR WHERE ((lineItem_LineItemType IN ('SavingsPlanCoveredUsage')) OR (lineItem_LineItemType IN ('DiscountedUsage'))) GROUP BY timeInterval_Month, lineItem_LineItemType, lineItem_ProductCode",
  "needBackLinkingForTags": true,
  "dataGranularity": "MONTHLY",
  "timeRange": {
    "from": "2025-08",
    "to": "2025-08"
  },
  "limit": -1
}

 

  • For spend based commitments savings you can validate the figure using the difference between the Unblended Cost and SavingsPlanEffectiveCost fields across all SavingsPlanCoveredUsage line item types.

  • For resource based commitment savings you can validate the figure using the difference between the Unblended Cost and the Reservation Effective Cost fields across all DiscountedUsage line item types.

  • To validate EC2 Savings from SPs you would want to look at the difference between the Unblended Cost and SavingsPlanEffectiveCost fields across the SavingsPlanCoveredUsage LineItemType where the product code equals AmazonEC2.

  • To validate EC2 Savings from RIs you would want to look at the difference between the Unblended Cost and ReservationEffectiveCost fields across the DiscountedUsage LineItemType where the product code equals AmazonEC2.