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:
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
}