Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Setting Up Collection > Native collectors > Amazon Web Services - deprecated > Mapping data to Cloud Cruiser

Mapping data to Cloud Cruiser

Table of contents

The Amazon Collector calculates usage for a given date by first identifying the authoritative Cost Allocation Report file for the target date (the file with the latest timestamp on that day). If no authoritative file exists for the target date, no usage is recorded for that date. Otherwise, the usage is calculated by taking the values from the target date's authoritative file and subtracting the values from the previous day's authoritative file. If the previous day has no authoritative file, the most recent day before the target date is used. If no days prior to the target date have an authoritative file, the target day's authoritative file is taken as the first of the billing period, and the values are read directly from the file, without any manipulation.

Feed configuration

The consolidated billing report data produced by Amazon is aggregated by user-defined Amazon tags. It is recommended that tags be assigned to all resources with values meaningful to the organization. A common example would be tagging each EC2 instance with an instance name. Amazon's billing data prefixes user tags with the literal string " user :" (so a user tag named Department would be reported by Amazon as user:Department ). By default, the " user: " prefix is stripped by the collector for processing. This setting is specified in the feed config, which can also define a list of tags to be excluded from processing. See AmazonFeedConfig for details.


Each line item of billing data is broken down by Amazon into four fields:

  1. CostBeforeTax
  2. Credits
  3. TaxAmount
  4. TotalCost

TotalCost is the sum of the other three fields. By default, the collector will only process the TotalCost field. AmazonFeedConfig ’s useTotalCostField parameter can be set to false to process the other three fields instead. If the TotalCost field is used, the collector will generate resource names directly from the Amazon usage types. For example,

  • EU-BoxUsage:m1.large
  • USW1-BoxUsage:t1.micro
  • DataTransfer-Out-Bytes

However, if the separate cost fields are used, each cost field will be reported as a separate resource. Resource names will be constructed by concatenating the cost field name to the usage type name:

  • EU-BoxUsage:m1.large-CostBeforeTax
  • EU-BoxUsage:m1.large-Credits
  • EU-BoxUsage:m1.large-TaxAmount
  • USW1-BoxUsage:t1.micro-CostBeforeTax
  • USW1-BoxUsage:t1.micro-Credits
  • USW1-BoxUsage:t1.micro-TaxAmount

NOTE: All resources are passthrough resource types.

Last modified


This page has no custom tags.


This page has no classifications.

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