Update to Costs of Amazon Kinesis Firehose

In the CloudHealth Platform, Amazon Kinesis Firehose was previously accounted for as an indirect charge. Now, the costs associated with Amazon Kinesis Firehose have been allocated to a new direct charge: ‘Kinesis Firehose’ and an indirect charge: ‘Kinesis Firehose - Other’. We recommend that you update your reallocation rules for Amazon Kinesis Firehose indirect charges. In addition, you can now allocate Kinesis Firehose charges into Perspectives and run configuration policies on them. While Amazon does not allow for tagging these assets, you can add custom tags to these assets in the CloudHealth platform for ease of reporting.

Tag Support for RDS Subnet Groups

We have added tag support for RDS Subnet Groups – you can see this reflected in the platform in the RDS Subnet Groups Asset Report, use them to allocate these assets (and all related resources) into Perspective groups, and run configuration policies based on tagging.

Update to Azure Cost History Report

We have recently made a change to the labeling of Azure services in the Azure Cost History Report. Previously, all direct charges were labeled “[service] - direct” in the table. Now, all charges will be categorized under either the ‘Direct Charges’ heading or ‘Indirect Charges’ heading. 

Note: This is a user interface update only. No changes have been made to your costs. 

Update to GCP Credits in the Cost History Report

Until recently, customer who received GCP credits could only see them reflected in CloudHealth as a separate charge and a separate tab in the Cost history report. With the recent change, we are now showing credits in the same way as we do for AWS and Azure, i.e. by default and as a line item in the Cost History report, represented as a negative charge.

Cross-Customer Report  -- General Availability

We now have the ability to report across customers for those in our partner community. This new report will show your customers’ cost history as well as the ability to see your margin across those customers. The report also includes drilldowns for the monthly data. You can access the reports under the partner console.

External ID Update for Partners

We’ve simplified the administration of AWS external IDs for partner console admin users. Partner admin users now have the ability to sync an external ID value between an end-customer tenant and the partner master tenant. You’ll see the option available on accounts with owner IDs that are currently not synced when editing accounts at the end-customer level.