April 2021 Release Notes
Manage existing API access keys with CloudCheckr CMx technology
You can now use CloudCheckr CMx access tokens when running API calls in our legacy product. You can still use your existing API access keys in the legacy product, but access tokens will provide better security, more consistent authorization management, and the ability to access multiple projects and accounts.
Set Azure currency in a Cost dashboard
If you have an Azure account that uses a currency other than the default option of US dollars (USD), you can now select from a list of available currencies on the Home page of your Azure account.
Updated the Account Export function
We made the following changes to our export function:
- Added a Credential Status column
- Increased the API page size to 100
- Changed the Provider Id column label to Provider ID
Access legacy and CloudCheckr CMx dashboards through the Overview list
When you open the Overview drop-down list on the Home page, you can now choose from dashboards created in our legacy product in addition to the new dashboards you create in CloudCheckr CMx.
Added two new panes to Custom dashboards
You can now choose from two additional pane options when building a dashboard:
- Table: allows you to view your data in a spreadsheet-style format
- 100% Stacked Bar: converts your values from absolute to a percentage of the total
Added a new column to the Users page
Added the User Level Access? column to the Users page under Settings > Access Management. This column will display Yes or No to indicate if a user has direct access to CloudCheckr CMx regardless if you have assigned a role to the user.
Updated the Historical Billing Summary report to display 18 months of data
Changed the Historical Billing Summary report to show 18 months' worth of data by default rather than 36 months of historic costs.
Updated the EC2 List of Reserved Instances report for CUR payers
We have updated the EC2 List of Reserved Instances report for Payer accounts based on the AWS Cost & Usage Report (CUR)—allowing our software to populate data directly from the CUR instead of applying our analysis to fields such as Instances Using Reserved Instances and Percent Consumed.