New API Capabilities: Unlock and Reprocess historical billing Reports (AWS & Azure)

Added new API calls that enable customers to get the status of, lock and unlock, and initiate reprocessing for a given month:
- AWS API calls
- Azure API calls

Use Case:

Customers chose to reload/reprocess data published by a Cloud Provider in order to ensure the most up-to-date costs are represented in the CloudCheckr platform. There may also be times that custom charges need to be updated across a wide range of projects in CloudCheckr, or some other adjustment needs to be made to multiple projects. It is now possible to programmatically query to check status, lock or unlock, and initiate a reload for a given project or set of projects within CloudCheckr.

Improvements

New Group By options have been added to the Advanced Grouping Report to allow deeper cost analysis (AWS and Azure)
- AWS
  - Invoice ID
  - Paying Account ID
  - Commercial vs GovCloud
- Azure
  - Paying Account ID
Added support for resource tag data for the AWS Elastic Container Service, which has also been added to BPCs and can be downloaded

Fixes

Addressed a performance issue with the historic billing collector which was causing extended cost ingestion times
Updated RDS Custom Oracle Single AZ RAC instance pricing after deprecation by AWS
Fixed an issue where Cost Changes Report was not loading
Enhanced descriptions in cost savings report CSV export
BPC export of “Large Exports” may now be downloaded
Resolved CSV column alignment issues impacting Inventory Reports exports
Fixed false positive issues with Azure BPC “App Service with SSL Disabled” and AWS Automatic RDS Database Backup”
Fixed issue with improperly tagged resources report where old rules were not being resolved
Addressed loading issues for EC2 RI inventory, Instance History, and History by Time reports (jobs expected to take a few days to complete)

MSP Reseller Link / L2 Customer Fixes

Resolved billing collector issue impacting reseller-linked projects (L2s) that prevented successful completion in certain scenarios
Ensured proper sharing of savings plan costs with reseller-linked projects (L2s) in specific edge cases
Fixed an issue where some Friendly Names were not being passed to an MSP’s L2 customer

April 7 30.2.2 release notes

Addressed an unexpected scenario where AWS included new EC2 instance types in the CUR file without making those instance types available via the Public AWS Pricing API (CloudCheckr relies upon the Public AWS Pricing API as part of the overall cost ingestion process) which caused some data ingestion to be incorrect
Addressed an issue accidentally introduced by a code refactor in v30.1.1 designed to improve performance under certain high-volume reservation purchase scenarios