We have updated the CloudHealth Migration Assessment to include VMware Benchmark Pricing, which gives industry standard benchmark pricing for virtual machines that run in VMware Data Centers. Previously, you needed to configure your own pricing using estimates. This was entered into the simple pricing setup in the CloudHealth Data Center Module, to get a base cost for your data center in the Migration Assessment.
With this private beta release, you can select “Benchmark Pricing” as an option in the Migration Assessment setup and automatically get industry standard benchmark pricing without having to configure anything.
In order for this to work, please ensure you are on the latest aggregator, namely
“Winter 2018 - 1.7.26 - VMware assets (1.7.26)” or later. If you are not setup to auto update please let your Technical Account Manager know, so they can update your aggregator.
If you are interested in taking part in this private beta, please contact migrationassessmentbeta@groups.vmware.com.

To provide easier and more complete visibility into amortized costs on AWS, CloudHealth will be consolidating our four separate amortization reports (EC2 RI Amortization, RDS RI Amortization, ElastiCache RN Amortization, and Redshift RN Amortization) into a single report, appropriately named the Amortization Cost Report. This new report will include all six reservable AWS services (EC2, RDS, RedShift, Elasticsearch, Elasticache, DynamoDB) and provides all-in-one visibility for:
Amortized costs
Recurring costs from the Cost History Report
Cost reallocation rules
Billing rules
If you would like to be granted early access to this feature, please contact your Technical Account Manager.

We are pleased to announce the WorkSpace Hours Usage Report which will enable you to report running costs and usage per WorkSpace resource for the past 13 months. You can now visualize aggregated WorkSpace costs and usage hours grouped by WorkSpace attributes.
To learn more about the WorkSpace Hours Usage Report, please view this Help Center article.

We have added four new policy conditions to help you identify non-confirming assets. You can now create policies based off of the number of shards in an AWS Kinesis Data Stream or the number of hosts attached to an AWS Elastic Load Balancer. You can also create policies to identify GCP Compute instances that are over a specific number of cores or RAM.
Additionally, we have added four new policies to help you manage your reservations in both AWS and Azure. You can now create policies to be alerted when Amazon RDS Reservations, Amazon ElastiCache Reserved Nodes, Amazon Redshift Reserved Nodes, and Azure Reservation Orders are approaching their expiration date.