Orbitera now supports Amazon Web Services’ Cost and Usage Reports for billing and cost management. If you enable Cost and Usage reports in AWS and give Orbitera access to the bucket containing the reports, Orbitera will automatically start processing your usage from the cost and usage reports. Please enable “Hourly” and “ResourceID” when enabling Cost and Usage reports, as in this screenshot:

This is also the same requirement for legacy detailed billing report import. To enable Cost and Usage reports if you haven’t already as a specific configuration is required. Orbitera will start processing your Cost and Usage reports once you have a full month of data available.

You should see no change to the amounts in your reports and invoices once you switch to Cost and Usage reports. Cost and Usage reports have several benefits over the legacy detailed billing report format:

  • Usage file are sharded, which allows them to be read in parallel
  • For Flexible Reserved Instances (RIs), NormalizedFactor and NormalizedAmount already exist in Cost and Usage reports making it easier to track how RIs are allocated
  • SKU matching is more robust as SKUs already exist in Cost and Usage reports
  • RI benefits are easier to track, including how they were applied, as ReservedID is created from the ReservedArn in Cost and Usage reports

There are a few changes to the format of the detailed billing report outputted by Orbitera once you make the switch to Cost and Usage reports:

  • Marketplace data will be always processed if the Cost and Usage reports contain marketplace usage. “Import Marketplace “ will no longer be an explicit option in AWS import jobs defined in Orbitera.
  • Billing features that exclude marketplace data (e.g. global discounts) will continue to function as before.
  • The UsageType will now reflect the actual type of instance that is consuming a Reserved Instance. In the legacy detailed billing report, when an RI benefit is applied to a line item in the detailed billing report, the line item reflects the type of RI that was applied rather than the actual instance type that received the benefit.In the new detailed billing report, the line item always reflects the actual instance type that received the benefit. In the example below, an c3.medium RI was applied to a c3.large instance. After switching to the Cost and Usage reports, the UsageType is be c3.large (the type of instance) rather than c3.medium (the type of flex RI that was applied).
    • Before:
UsageType ItemDescription
SAE1-HeavyUsage:c3.medium
USD 0.000000 hourly fee per Linux/UNIX,
c3.large instance; UsageType: 
SAE1-BoxUsage:c3.large
    • After:
UsageType ItemDescription
SAE1-HeavyUsage:c3.large
USD 0.000000 hourly fee per Linux/UNIX, 
c3.large reserved instance applied
  • EC2 RI Cost (partial-upfront, no-upfront) is now be charged in the summary row following the format of non-EC2 RIs
    • Before:
UsageStartTime UsageType Quantity UnBlendedCost
2018/03/01 00:00:00 HeavyUsage:c3.large 1 $1
2018/03/01 01:00:00 HeavyUsage:c3.large 1 $1
2018/03/01 02:00:00 HeavyUsage:c3.large 1 $1
…..
2018/03 HeavyUsage:c3.large 0 $0
    • After:
UsageStartTime UsageType Quantity UnBlendedCost
2018/03/01 00:00:00 HeavyUsage:c3.large 1 $0
2018/03/01 01:00:00 HeavyUsage:c3.large 1 $0
2018/03/01 02:00:00 HeavyUsage:c3.large 1 $0
…..
2018/03 HeavyUsage:c3.large 744 $744

Amazon Cost and Usage reports contain historical data from the date they are turned on. As always, if you have any questions please reach out to support@orbitera.com