Bugs

• Fixed an issue where the Azure get_detailed_billing_with_grouping_by_currency API endpoint could return an endless 202 response loop when querying billing periods with no data. The endpoint now correctly returns a 200 response with no data, eliminating the need for workarounds when retrieving historical Azure billing data.
• Fixed an issue that prevented newly discovered accounts from being added to an Account Family which had that auto-assign preference set.
• Fixed an issue where the AWS Billing Collector job failed for accounts using the "Bring Your Own Media" RDS license model. An unrecognized license model value caused billing collection to crash during Reserved Instance unsharing, preventing cost data from updating for affected customers.

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.

• At Re:Invent 2025 AWS announced changes to their Support Plan offerings. CloudCheckr now supports both Unified Operations and Business Support+ plans.

  • The application will continue to support the legacy Business Support plan until January 1, 2027 per the guidance and published plans of AWS. This will remain as a dedicated option for new cost ingestion until AWS no longer supports this plan.

  • Historical month reload notes:

    • For billing months in accounts prior to Dec 2025 that are now on a new plan type, should a billing month before Dec 2025 require reprocessing, CloudCheckr will automatically apply the legacy plan for that specific month during reprocessing. For example: 

      • Account 1234 currently has Business Support+ configured; if the month April of 2024 is reprocessed, CloudCheckr will apply the older Business Support logic to the April 2024 bill during reprocessing.
      • Account 5678 currently has Unified Operations configured, and the month April of 2024 is reprocessed; CloudCheckr will apply the older Enterprise Support logic to that month's bill.

• When attempting to delete a saved filter that is associated to a configured invoice, the application will warn the user and ask for confirmation that they do indeed wish to delete the saved filter that would typically be used to create invoices.

• Resolved an issue that prevented certain Custom Usage Rates from being correctly applied to List Cost.
• Resolved an issue preventing users from creating and/or updating changes to User Groups within the Core UI.
• Resolved an issue where certain Custom Billing Charges where not being applied correctly for AWS accounts when the AWS listed rate was $0.00/NULL. A reload of the month will correct the issue for historical months affected.
• Resolved an issue where configured PDF invoice reports were scheduled to be uploaded to an S3 bucket was instead only generating CSV files.
• Resolved an issue with CSV export of the RI Recommendations report that prevented all available columns being included in the export.

Improvements

• Several enhancements have been added to the Invoice Generator functionality.

  • When manually recreating an invoice, users now have the ability to select which month they want to recreate.
    
    

     

  • On the Historical Invoice page, users will now see columns that give additional context to the invoice that was generated. 

    • Saved Filter - If the invoice is configured from a saved filter, this will display the name of the saved filter.
    • Margin % - This will indicate the overall margin of the invoice created, as defined by (“List Cost” - “Unblended Cost” ) / “Unblended Cost” * 100

    • Status - This will indicate the date that the invoice was sent if it was successfully generated.

      
      

• When generating a large export from Advanced Grouping Report, users now have an option to give the export a custom name.

Bugs

• Resolved an issue for MAV Best Practice Check assessment results that prevented all child account assessments from being included in the larger MAV assessment.

• Resolved an issue where AWS Custom Usage Rates configured within CloudCheckr were impacting Free Tier $0 rows.

Improvements

• Scheduled invoice view has been improved through the addition of the Group By column, where we added additional details to improve identification of invoice details.
  
  

   

• Advanced Grouping email configuration has improved in-app help text to clarify the expected email behavior when configured from this screen. 

Bugs

• Resolved an issue where the data export for the Reserved Instance Recommendation report was exporting as a JSON, instead of a csv as expected.
• Resolved an issue that prevented some users from expanding scheduled invoices to view and edit details.
• Addressed an issue that prevented some customers from disabling the single-month consolidated billing summary email.
• Resolved a bug with API edit_custom_billing_charge_percent_all_charges_v3, which prevented API users from editing existing custom charges.
• Solved an issue that occurred when generating PDF invoices from saved filters that included certain group-by conditions, resulting in unexpected formatting issues.

Improvements

• User Experience updates to the RI Recommendations and Cost Savings reports.

  • Updated default columns to include “Instances to Purchase,” which describes the total number of recommendations to purchase per instance type. This column remains available on the CSV export (which also contains additional columns not in the UI).
  • Improved readability of certain data points.
  • Enhanced in-app help text to clarify differences between real-time RI Recommendations (pulled directly from AWS Cost Explorer) and snapshot-based Cost Savings reports, including details on data freshness and assessment criteria.

  • Added proactive in-app notification banners on the CMx Dashboard and Core BPC pages to alert users when their IAM policy is missing the required ce:GetReservationPurchaseRecommendation permission needed for the new RI Recommendation page and BPCs, guiding users to update their IAM policy to access the latest recommendations.

    • Updated logic ensures that only accounts with the correct permissions and feature enablement will display BPCs and recommendations.
  • RI Recommendation BPCs are now hidden (not shown as green/passing) when required permissions are missing or the feature is not enabled, preventing misleading results.

Bugs

• Resolved an issue where the RI recommendations report would export results to a JSON file rather than a CSV as expected.
• Resolved an issue for monthly emails configured from a saved filter that prevented the email from being sent if the month was not yet finalized.
• Resolved an issue where, when a default account family is enabled, the auto-assign feature was failing to successfully assign new accounts to that default account family.

Improvements

• Filter capabilities for Azure One-Time Charge report has been enhanced. Users are now able to filter down this report to view targeted charges.
• Added support for the value Transaction Type for the parameter of filter_type to the create_detailed_billing_grouped_filter_v2 API response.

Bugs

• Resolved an issue that prevented scheduled Daily Emails from being sent out consistently.
• Addressed an issue on the Cost BI report where adding Tag Keys would remove the cost columns from the export of the report.
• Resolved an issue that prevented users from saving new or making updates to CMx Dashboards.
• Resolve an issue that prevented newly discovered accounts from being applied to the Default Account Family automatically.

New Features

New AWS RI Recommendations, new Best Practice Checks  

CloudCheckr has built a new AWS RI Recommendation report for payer accounts that can be generated against the following services:  

• Amazon EC2 (Elastic Compute Cloud) – For virtual server instances
• Amazon RDS (Relational Database Service) – For managed relational databases
• Amazon ElastiCache – For in-memory data caching
• Amazon OpenSearch Service – For search and analytics workloads
• Amazon Redshift – For data warehousing and analytics
• Amazon MemoryDB for Redis – For Redis-compatible in-memory databases
• Amazon DynamoDB – For NoSQL database workloads 

These recommendations will help you identify cost-saving opportunities by analyzing your historical usage and suggesting reservations that could reduce your on-demand spending. 

When generating these recommendations, the engine automatically excludes any instance usage that's already covered by existing Reserved Instances, Savings Plans or Spot Instances. This ensures that you receive recommendations only for the actual uncovered On-Demand usage. Specifically, EC2 RI recommendations are now aware of purchased savings plans and now take them into account during the recommendation process.  

If utilizing CMx, access the report by navigating to Home > Cost Savings > RI Recommendations. If utilizing Core, access the report by navigating to Cost > Reserved Usage > Recommendations > RI Recommendation. You can also search for RI Recommendations in the report search bar at the top of the application. 

This new report replaces the legacy RI Recommendations page, which had reduced levels of functionality relative to the new page.  

Prerequisites 

To get the new RI Recommendation page and the below BPCs to work as expected, the IAM Policy configured for your account must have the following permission: ce:GetReservationPurchaseRecommendation  

New Best Practice Checks  

Along with a new AWS RI Recommendations report, we are releasing several new Best Practice Checks (BPCs) to all customers (Core and CMx users) related to these newly supported services, and additionally have updated existing BPCs to utilize the new recommendation engine. 

New BPCs: 

• MemoryDB Reserved Instance Purchase Recommendations 
• OpenSearch Reserved Instance Purchase Recommendations 
• DynamoDB Reserved Instance Purchase Recommendations 

Updated BPCs: 

• RDS DB Instances Reserved Instance Purchase Recommendations 
• EC2 Reserved Instance Purchase Recommendations 
• ElastiCache Reserved Instance Purchase Recommendations 
• RedShift Reserved Instance Purchase Recommendations 

Other Improvements

• Added ability to configure exact days of monthly emails sent for Azure MAV reports; Billing Daily Summary & Billing Consolidated Summary
• Improved flexibility of get_detailed_billing_with_grouping_by_currency API date range query.

Bugs

• Resolved API issue for get_detailed_billing_with_grouping_by_currency where the start date couldn’t be set to before a project create date.

Cost Savings report improvements

• The cost savings report has been improved to clearly show where and how to achieve maximum savings. The page has been split into two possible monthly savings sections to highlight the recommended two-step approach to achieve optimal savings. 

  • The first step/section is targeting mis-provisioned resources that should be resolved first.
  • The second step/section is isolating RI purchase recommendations. After resolving all possible or desired mis-provisioned resources, it is recommended to wait 7 days before purchasing the RI recommendations. This allows the recommendation engine to adjust for new usage patterns.

• Now both RI and SP recommendations are pulled from AWS, and surfaced within the application at both L1 and optionally L2 directly-credentialed payers. 

Other Improvements

• Improved Credit handling for SPP credit sub-types. Previously, sub-types of SPP were not being captured in alignment with configuration of the SPP (Solution Provider Program) credit type.

• Improved the behavior of Azure RI and SP un-sharing as it relates to Force initial list cost to be based on Pay As You Go pricing configuration. The behavior is now consistent between both Asure RI and SP. If Force initial list cost to be based on Pay As You Go pricing is enabled, it will reset the list cost for all costs except for Reserved Instance and Savings Plan costs by default. If the user wishes to reset list cost for RI and SP, they will need to explicitly enable un-sharing for each of them.
  

Bugs

• Updated Cost BI CSV export to only include columns that are enabled on the table.
• Resolved an issue for Azure Advanced Grouping that generated an error when attempting to drilldown into the chart.
• Resolved an issue where billing data was not properly reloading for Azure GOV CSPs when Marketplace charges were found.

Improvements

• Added additional summary and detailed inventory reporting for AWS EKS and MSK services. These reports are available for both single-account and MAV reporting needs.
• Added support for Austria East region for Azure.

• Daily Cost Alerts now evaluate based on the “last day in the billing file at time of data ingestion minus one”.  This approach improves the reliability of alerts by ensuring that ingestion for a given day completes and the cost alert is evaluated properly against the defined criteria.  

  • For example, today is the 22nd, and the latest billing file ingestion completed included data from the 21st. The alert would thus evaluate and fire an alert on data from the 20th to ensure the full day of data is evaluated for the alert.

• Correction from last release note: We incorrectly reported on a new property to the get_account_Family_v2 API endpoint. We have updated the release note to the following:

  • An associated API endpoint, get_account_Family_v2, has been updated to include a new boolean property, "DefaultAccountFamily": True, to define if the family is default or not.

Bugs

• Resolved an issue introduced by Azure unexpectedly updating the format of ReservationOrderId which prevented Azure Reservation Purchases from being reported. Customers might need to reload June data for accurate cost data.
• Resolved an issue where ‘Not Set’ resource group text was missing from generated invoices.
• Resolved an issue where List of VMs was not reporting on VMs belonging to a Scale Set.
• Resolved an issue where the BPC report and snapback reports would not load for MAV and all account types.
• Resolved an issue where several APIs would unexpectedly return a 400 - Project Is Not Credentialed error when querying for a date range that contained valid data.
• Resolved an issue where an Azure MAV change monitoring report included results from AWS resources.
• Addressed an issue when accessing the binoculars when attempting to create a new custom charge page, became unresponsive