Support for AWS Database Savings Plans

• AWS Database Savings Plan were supported natively in CloudCheckr when Savings Plan Deallocation was configured, and now supports Database Savings Plan when Savings Plan Unsharing is in use.

  • Savings Plan Unsharing lets you avoid AWS Savings Plans from automatically applying discounts to all linked accounts within an Account Family, and instead restrict or redirect where those benefits are applied. This gives organizations more control over how Savings Plan discounts are allocated and reported across business units or customers.
  • Savings Plan deallocation lets you selectively remove or “turn off” specific AWS Savings Plans discounts from applying to accounts that are not the purchasers of the savings plan, or are not within the account family of the purchases. This helps partners and enterprises better control which customers or business units receive Savings Plan benefits and how those savings are reported.
  • If you have already configured Savings Plan Deallocation or Savings Plan Unsharing, no additional configuration is necessary.

Other Improvements

• Added support for new terms on Azure Reserved Instances. Supporting 1 month and 120 months options.

• Added support for the “NOT” operator on filters for Azure Advanced Grouping.

Bugs

• We addressed a platform-wide issue impacting AWS data ingestion occurring as a result of lack of proper API response from AWS in their Middle East Region, likely the result of ongoing AWS recovery efforts in UAE and Bahrain. 
• Resolved an issue with the Billing and Cost Management Dashboard report that prevented forecasted data from displaying on the report when a MAV was selected and not all Payees within the MAV were credentialed.
• Fixed an issue where the AWS Cost and Usage Report import jobs were failing under certain edge conditions, preventing billing data from loading. 
• Fixed an issue in Advanced Grouping where List Cost description rows could expose underlying Unblended rate details for some AWS payer accounts starting in March 2026.
• Fixed an issue where the AWS Cost Changes report incorrectly showed “No data for this report” when comparing costs across two different billing periods.