Import of Historical Cost AWS Data
search cancel

Import of Historical Cost AWS Data

book

Article ID: 284359

calendar_today

Updated On:

Products

CloudHealth

Issue/Introduction

To setup historical CUR data directly at the customer tenant, verify the proper format, and attempt to import up to 13 months of data you must have the following:

  • CUR in the source bucket must be defined in the manifest.
  • Check your report path in your AWS Billing Console, and make sure not to include any preceding or trailing slashes when inputting the report path.

Resolution

The report path should just be whichever sub-folder you see in the console.

It would be: "cht-hourly", rather than "cht-hourly/" or "/cht-hourly-with-resource-ids".

  • Double-checking your CHT IAM policy and make sure that permissions have been added to read the CUR.

Once you have saved the files in the bucket in the proper format, the platform will be able to pull your CUR without issue.