We have released a new feature to give you further control over the AWS Partner Billing engine. Now available on the Admin > Settings page, you can control whether CloudHealth filters out tax line items through partner billing for all your customer tenants. If updated, this will only apply to the open month(s). Please note that this applies to all billing configurations (e.g. Consolidated, Full Family).

We are introducing the same source of collection (single snapshot of BigQuery) for both history invoice and cost history, a significant enhancement to the current way of sourcing these two reports. All customers will have an enriched experience in the platform with improvements such as:
Consistency between reports
More efficient data collection & processing
Improved resource management with both reports powered by a single collection
With SKU automation, we are taking customer onboarding to the next level. Once customer billing accounts are configured in the CloudHealth platform, subsequent onboarding actions will be completely automated without any manual intervention. All new GCP SKUs and services will be identified by the platform itself and will be categorized as “Service – other” by default. As an effect of this update, the existing “Other Products” category will be dissolved into actual SKU categories. For more details please, please refer to the documentation.
The latest addition to our growing list of policy conditions includes operational governance use cases for Expiring Reservations and Virtual Network Gateways. For these resources, the following policies are now available:
Reservations:
Upcoming Expirations
Tagging governance (identify untagged reservations, reservations missing a particular tag, pattern matching on tags, etc.)
Virtual Network Gateways:
Unused (no IP addresses associated)
Tagging governance (identify untagged VNGs, VNGs missing a particular tag, pattern matching on tags, etc.)