Locale selector icon
Jul202016

GCP Billing Account Configuration API

We’re pleased to announce our new GCP Billing Account Configuration API. You’ll now be able to use this API to create, update, and delete your GCP Billing Accounts programmatically.

As a partner, you will also be able to pass in the customers client ID, along with your partner-level user API key, to manage the Billing Accounts within all of your customer tenants in CloudHealth. View the API documentation. 

GCP BigQuery Master Billing Account Support

We’re pleased to announce support for collecting billing data for partner sub-billing accounts from their single master billing account BigQuery export. Now possible using the Billing Account API, you can configure new, or update existing, Billing Accounts to leverage your master billing account export table for costs. 

To leverage this feature, you’ll need to use two service accounts; one that will be used to collect your billing information and will live in your own organization, and another that will be used to collect the customers asset information and will live in their organization. 

FlexReports - Public Beta

We’re excited to release the public beta of CloudHealth FlexReports (initially for AWS only), which provide you the ability to report on cost, usage, and asset data within a single report. These reports will empower financial users to do granular analysis to understand cost drivers at the asset and tag level. You will also have access to an API backed set of capabilities to define and export reports formatted to suit your specific needs. Our goal for this feature is to provide more timely insights to drive decision making within your pipeline and governance process.  

We’re starting with the AWS CUR and will be adding additional clouds, Perspectives, cost reallocation rules, and other data enrichments to create a comprehensive reporting solution over time. You will have a minimum of 6 months of historical CUR data to begin with and eventually 13 months of historical data will be available to query.

Learn more about CloudHealth FlexReports in this Help Center article and API documentation.

AWS Reserved Instance Apportioning Enhancement

We’re always looking for ways to enhance our reporting capabilities to increase visibility for key cloud services and infrastructure. To that end, we’ve been focusing our time and attention toward Reserved Instance apportioning in AWS. CloudHealth has historically calculated apportioning of recurring RI costs for some of the reservable services, but we are changing our approach by leveraging data available in the AWS Cost & Usage Report. Since we are now getting this data from the source, not only does this improve the precision of apportioning, but it will provide apportioning support for all reservable services (EC2, Redshift, ElastiCache, ElasticSearch, RDS, and DynamoDB) in all time granularities (hourly, daily, weekly, monthly) in their associated cost & usage reports. 

The enhanced reports can be found in the platform under Reports > Cost:

The new apportioning logic is in effect as of July 1, 2020. If you’re interested in the new apportioning logic for all historical months, please open a support ticket and we can enable that for you.

New AWS Indirect Costs

We have added indirect cost categorization for Amazon AppFlow, Amazon Augmented AI, Amazon Chime Business Calling a service sold by AMCS LLC, Amazon Chime Call Me, Amazon Chime Voice Connector a service sold by AMCS LLC, Amazon Detective, Amazon Elastic Inference, Amazon Fraud Detector, Amazon Quantum Ledger Database, AWS CloudFormation, AWS CodeArtifact, AWS IoT Events, AWS IoT Things Graph. These services are now represented as their own Indirect Costs, which could be assigned to Perspective Groups using cost reallocation rules. Previously, these charges were included under Indirect service item - ‘Other’.