Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 > Collecting, transforming, and publishing > Amazon Web Services > Flows in the Amazon Web Services template

Flows in the Amazon Web Services template

Table of contents
No headers

The Amazon Web Services workbook template includes several flows that consolidate service and usage information to a simple format that allows you to understand how to charge for the actual usage of specific AWS services.

For detailed information about the raw data collected from AWS, see Dimensions and measures collected from AWS.

Flow Description
Ownership Imports resource-ownership data from the ResourceOwnership collection, and then creates lookup files that are used by later flows to associate owners and departments to specific resources. This flow is useful when you are not using AWS tags to associate departments and owners with resources.
ImportServices Collects AWS service data from the AWS1 and AWS_EndOfMonth collections, and then removes all measures with a zero value. The flow converts the collected UsageQuantity measure to a dimension named UnitsDescription, and then to ensure that it keeps only the data that is relevant and useful, the flow deletes all dimensions except ComputedServiceName, ItemDescription, and UnitsDescription. The flow provides a value of units to any empty UnitsDescription fields, and then aggregates and publishes the transformed service data.
PublishUsage Collects daily usage data from the AWS1 collection and then aggregates the data. It then determines whether it should retrieve owner and department information from AWS tags or from data you entered in the ResourceOwnership.csv file, based on the the value of the UseOwnershipFile workbook parameter. If it uses the file, the flow obtains owner and department information from the lookup files created by the Ownership flow. If the flow cannot locate an owner or department, it sets the related Owner or Department dimension to Unknown.

The flow also calculates VM sizing data for Virtual Machine records, and then compares that data to standard VM sizes defined in the lookup tables you imported. For VMs that fall outside of the definitions in the lookup table, the flow marks those records as nonstandard. For more information, see VM sizing guidelines for CloudSmart-Now.

The flow deletes unnecessary dimensions and sets the OperatingSystem dimension to Linux, RedHat, or Windows. Lastly, it publishes the transformed data to your Cloud Cruiser database, allowing you to charge for the actual usage of the services collected by the ImportServices flow.

PublishEndOfMonthUsage The PublishEndOfMonthUsage flow works almost exactly as the PublishUsage flow. The only difference is that the PublishEndOfMonthUsage flow uses the AWS_EndOfMonth collection, which has the End Of Month Mode enabled. This ensures that the ImportServices flow imports data from a monthly invoice instead of daily invoices.
ImportCustomers Imports data from the PublishUsage and PublishEndOfMonthUsage datasets, and then removes all measures, and all dimensions other than Owner and Department. It aggregates and publishes Owner data, and the aggregates and publishes Department data.
HandleUnknowns Alerts you about any resources that do not have assigned owners and departments. It begins by importing data from the PublishUsage and PublishEndOfMonthUsage datasets, removing all measures, and removing all dimensions except for ResourceGUID, Owner, and Department. The flow then scans the Owner and Department fields for a value of Unknown. For every Unknown value, the flow generates an exception message visible in the Data > Processing > Monitoring area of Cloud Cruiser.
Cleanup Removes any files from your <workingDirectory>\processing\AWS directory that are more than 1 day old, as these files have already been processed and are no longer needed. AWS billing files can be very large. If you have available disk space on your Cloud Cruiser server, and you would like to retain your files for more than 1 day, modify the Retention Days value in the Clean Up Directory step of this flow.
Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP