Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Winter '23 Release

NEW FEATURES

Azure MCA Billing ROAD-106 - Getting issue details... STATUS

Microsoft introduced a new licensing agreement requiring customers to migrate from Enterprise Agreement to Microsoft Customer Agreement. Cloudaware adds support for MCA billing type to enable customers to continue using Azure Cost Management in full. Learn more: https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/migrate-cost-management-api

UPDATED FEATURES

AWS Amortized Costs

Cloudaware supports amortized costs calculations. Customers using AWS Reservations such as Amazon EC2 Reserved Instances can better understand how AWS spending is distributed across billing periods. Leverage Cloudaware advanced analytics

Learn more about cost datasets types in AWS: https://aws.amazon.com/blogs/aws-cloud-financial-management/understanding-your-aws-cost-datasets-a-cheat-sheet/

Custom Fisсal Periods

Cloudaware consumes billing data files from cloud vendors as is. Some reports, such as AWS Cost and Usage Reports (CUR), provide more detailed cost and usage aggregations by hour or day. However, these metrics are still based on a calendar. For every line item, metrics such as 'Usage Start Date" and 'Usage End Date' don't give ground for calculating a resource cost for a specific unit of time.

Cloudaware offers a new approach to cost management under custom fiscal periods:

Cloudaware offers a new approach to cost management under custom fiscal periods. First, a customer describes their fiscal period structure. Next, using advanced logic in Google BigQuery, Cloudaware maps the calendar and custom fiscal dates to generate a unified dataset containing both the 'Report Year-Month' metric and a metric indicating customer-defined fiscal periods. Then, Cloudaware uses this dataset to visualize cloud costs based on customer-defined fiscal periods in the Cloudaware BI Analytics portal:

NEW SERVICES


UPDATED SERVICES
TunHub for VMware vCenter

Cloudaware extends Breeze functionality to support vulnerability scanning of VMware vCenter virtual machines. VMware vCenter doesn't have metadata to retrieve the unique id required for mapping VMs that need to be scanned and ids of Breeze agents installed on those machines. By employing the field 'identityBiosUuid', Cloudaware matches vCenter VMs and Breeze agents ids to simplify Breeze deployment in vCenter and scanning of vCenter VMs at scale.

  • No labels