Locale selector icon
Oct201825

Update To Costs of Elasticsearch RIs and Contact Center Telecommunications -- Coming Soon

We will be introducing new items in the Cost History Report for Elasticsearch RI Prepays and Contact Center Telecommunications. Previously, ElasticSearch RI Prepays were included in the Elasticsearch - Other direct cost and Contact Center Telecommunications was included in the Other indirect cost. Going forward, they will appear as their own indirect charges.

We recommend that you update your reallocation rules for Elasticsearch - Other and create new ones for the newly introduced indirect charges.

Cost Allocation by Billing Tags for Additional AWS Services -- Coming Soon

As previously announced, we are developing a more comprehensive approach for extracting asset attributes from bills to allocate costs for AWS services.

We will soon be using the tags and resource ID from your bill to automatically allocate AWS Glue, Amazon Appstream, Alexa For Business, AWS Certificate Manager, AWS IoT Analytics, AWS Secrets Manager, and AWS Storage Gateway costs and assets to the appropriate Perspective groups. Costs for these services will be distributed into the following direct charges:

  • Glue - Development Endpoint

  • Glue - Job

  • Glue - Crawler

  • AppStream - Image Builder Instance

  • AppStream - Fleet Instance

  • AppStream - User Fees

  • IoT Analytics - Channel

  • IoT Analytics - Pipeline

  • IoT Analytics - Datastore

  • IoT Analytics - Dataset

  • Storage Gateway - File Share Request

  • Storage Gateway - Tape Storage

  • Storage Gateway - Tape Request

  • Storage Gateway - Volume Gateway Storage

  • Storage Gateway - Volume Gateway Request

  • Alexa for Business - Shared Device

  • Alexa for Business - Enrolled User

  • Certificate Manager - Certificate

  • Certificate Manager - Certificate Authority

  • Secrets Manager - Secret

And the following indirect charges:

  • Glue - Development Endpoint

  • Glue - Job

  • Glue - Crawler

  • Glue - Data Catalog

  • Glue - Other

  • AppStream - Other

  • IoT Analytics - Other

  • Storage Gateway - Other

  • Alexa for Business - Other

  • Certificate Manager - Other

  • Secrets Manager - Secret

  • Secrets Manager - API Call

  • Secrets Manager - Other

This allocation will be applicable to the past 13 months. We recommend that you save your cost and usage reports for reference. If you haven’t already, please enable all the tags in your bill that you use for Perspectives.

Learn more about activating user-defined cost allocation tags in this AWS Documentation article.

Support for Additional AWS Services

Amazon API Gateway, AWS CodeBuild, AWS Directory Service, Amazon Machine Learning, and ELB v2 costs were recently updated to be distributed into the following direct charges:

  • API Gateway - API Call

  • API Gateway - Caching

  • API Gateway - Data Transfer

  • CodeBuild - Build Minutes

  • Directory Service - Standard Edition

  • Directory Service - Enterprise Edition

  • Machine Learning - Compute

  • Machine Learning - Prediction

  • EC2 - Application Load Balancer Transfer

  • EC2 - Application Load Balancer Usage

  • EC2 - Network Load Balancer Transfer

  • EC2 - Network Load Balancer Usage

And the following indirect charges:

  • API Gateway - Other

  • CodeBuild - Other

  • Machine Learning - Other

  • Directory Service - Other

Also, for the AWS services mentioned above, we now use the tags and resource ID from your bill to automatically allocate costs and assets to the appropriate Perspective groups. This allocation is applicable to the past 13 months as well.

Learn more about supported AWS services in this Help Center article.

Support for GCP Resource-based Pricing 

As of October 1st, Google Cloud implemented “Resource-based Pricing” as the new way to calculate the cost for Predefined Machines.

Previously, Google Cloud provided information about the number of cores associated with a Predefined Machine in the Billing and Usage CSVs. Moving forward this information will no longer be provided. As a result, the following CloudHealth reports have been impacted:

  • For the Compute Engine Cost Report, the existing Machine Profile and Machine Type measures cannot be used for data starting on October 1st. These have been renamed to Machine Profile (deprecated October 1) and Machine Type (deprecated October 1). Two new categorization options have been added that can be applied to costs from October, Resource Profile and Resource Type.

  • The Compute Engine Usage Report is now named the Predefined Compute Instances Report. Custom Machines will no longer be included in this report.

  • For the Compute Instance Hours Report, only usage by Custom Machines will be displayed starting October 1st. All usage prior to October 1st has not been impacted.

Learn more about CloudHealth support for GCP Resource-based Pricing in this Help Center article. 

Expansion of CloudHealth Academy Videos & New Video Navigation

We have expanded our video offerings to include new videos on: Containers, Cost Reallocation, GCP Budget vs. Actual, GCP Billing Statements, AWS Unused RI, AWS Savings Report, AWS Security Recommendations, AWS Custom Security Policies, and AWS Open Ports. Check them out in CloudHealth Academy.

In addition, we have added a new user friendly way of navigating videos within CloudHealth Academy. Go to the upper left help menu and select "Browse Our Help Videos".

October 25, 2018