We’re excited to announce that we have made a refreshed and revamped version of our existing API documentation generally available. The guide is accessible publicly and is not behind a login. You can access the new API Guide at http://apidocs.cloudhealthtech.com.
The refreshed design provides:
A streamlined and familiar interface for you to learn about our API
Detailed documentation of all REST endpoints along with the parameters they expose
Simple examples to get you started
You can contribute to and provide feedback on the API Guide by creating issues and pull requests in our public Github repository (https://github.com/CloudHealth/cht_api_guide).
We’re pleased to announce the private beta of CloudHealth’s integration with Slack. You can now receive Slack notifications for policies that have been violated in the CloudHealth platform. You must have administrator privileges to enable the CloudHealth bot in your Slack workspace.
Learn more about the Slack integration in this Help Center article.
If you are interested in joining this private beta, please contact slack-beta@cloudhealthtech.com.


We have added a new feature to allow for delivery of subscribed reports to a customer provisioned S3 Bucket. All the options that are available for Email Subscriptions are now available for S3 delivery. When you subscribe to a report you will see the choice to “Deliver As,” where you can choose “Email” or “S3 Bucket” as the delivery type. As part of this feature we have also added support for JSON format for both Email and S3 Bucket Subscriptions. Learn how to configure a S3 Bucket to receive subscriptions in this Help Center article.
If you are interested in joining this private beta, please contact jwilkinson@cloudhealthtech.com.


We have added indirect cost categorization and aggregate cost policies for Amazon DynamoDB Accelerator. This service is now represented as its own Indirect Cost, which can be assigned to Perspective Groups using cost reallocation rules. Previously, it was included under Indirect Costs - ‘Other’.
We have added tag support for RDS Snapshots – you can see this reflected in the platform in the RDS Snapshots Asset Report, use them to allocate these assets (and all related resources) into Perspective groups, and run configuration policies based on tagging.
In the CloudHealth Platform, Amazon Kinesis Firehose is currently accounted for as an indirect charge. In the near future, the platform will be updated so that costs associated with Amazon Kinesis Firehose is 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. If you update your IAM policy using the auto-generated IAM policy in the platform, no further action is required. If you update your IAM policy manually, there are additional permissions that you need to add to your IAM policy:
firehose:DescribeDeliveryStream
firehose:ListDeliveryStreams
Learn more about updating AWS account policies in this Help Center article.
We recently added support for additional Azure Virtual Machine sizes and series, including DS11 v2, DS12 v2 , E64 v3, Standard Esv3 series, and the Standard Lv2 series. Support for these virtual machines is reflected across the platform.
