Cost & Usage Reports (CUR) have replaced Detailed Billing in AWS. CloudWisdom requires Cost & Usage Report data and no longer supports Detailed Billing files.
Already have an existing Cost and Usage Report with GZIP or ZIP compression set up? Great! Skip to part 2 of this guide.
CostAndUsageReports. Do not include any leaning or trailing forward slashes; doing so may distort the file hierarchy output by AWS.
It can take up to a few hours for data to populate in the S3 bucket.
If you have just created your IAM role, wait 2-5 minutes for AWS to finalize its creation before proceeding to these steps. This ensures the new role has the correct s3 access permissions when added to CloudWisdom.
If the Report Path Prefix lookup is not available (and is instead a freeform text input), make sure you are using the most recent IAM role available. You can create the latest IAM role using the our CloudFormation script. You also have the option to manually enter the S3 Bucket Name (chosen in section 1, step 7) and Report Path Prefix (created in section 1, step 8).
The following best practices ensure optimal Cost & Usage report setup.
Some customers store their billing files in a shared master billing account and need to grant CloudWisdom restricted access to one specific S3 bucket. You can use the master billing account permissions to create a limited read-only IAM role when configuring your AWS integration with CloudWisdom.
For customers using a shared S3 bucket: CloudWisdom only reads the costs for accounts that we monitor; data for unrelated accounts is discarded.