Apr201925

Update to Partner Account Assignments API — Billing Families Support

Today, we’re extending the capability of our Partner Account Assignments API to allow for more robust account assignment conditions. The Version 2 API now supports standalone, consolidated, and full family pass through account construct combinations, so you can programmatically configure your customers complex account setups.

Please note that this is being released as a new version of the API. Existing functionality built on Version 1 is not impacted by this update. For more details, see the CloudHealth API Documentation.

Update to CloudHealth API Authentication Requests — Action Recommended

When you make a request through the CloudHealth API, your unique API key identifies and authenticates you as the originator of the request. Previously, you could specify your API Key as a query parameter attached to an API endpoint. Now, the API has been updated to allow you to pass your API key as an authorization header. This is how authentication now works:

curl -H ‘Authorization: Bearer XXXXX98900000YYYY’ -H ‘Accept: application/json’ ‘https://chapi.cloudhealthtech.com/olap_reports/cost/history?interval=monthly’

This new approach is more secure and reduces the risk of your API key being intercepted or stored in server logs. If you have scripts that use the previous method of authenticating API requests, we recommend that you update those scripts to use this new method. The CloudHealth API Documentation has been updated to reflect the new method.

New Policy Conditions Added — Governance and Security

We have added support for seven new policy conditions to help govern and secure your AWS infrastructure.

Governance policies to identify:

  • Instances based off of any instance type to help protect you against unexpected usage. For example, a policy could be used to identify and stop any instances launched that are larger than 16xlarge.

  • EBS volumes that are over a certain size.

  • EBS volumes that have more than a specified number of snapshots.

  • Images based off of the number of instances launched from it.

Security policies to identify:

  • Volumes that are unencrypted.

  • IAM Users with no access keys.

  • Security Groups that have a specified port open.

New Categories in Data Center Cost History Report

We have released three new categories in the Data Center Cost History Report, namely Clusters, Data Centers, and Hosts for VMware accounts. This will allow cost to be shown at these groupings rather than just at the machine level which was previously supported.

Support for GCP Dataproc Clusters

We have recently added collection and reporting for Google Dataproc Clusters. This asset type is now available across the platform including Perspectives and Policies.