Cost & Usage Reports (CUR) have replaced Detailed Billing in AWS. These reports publish your AWS billing reports once a day in CSV format to an S3 bucket that you own. CloudWisdom uses these reports to analyze your resource costs and right sizing needs.
CloudWisdom no longer supports Detailed Billing files.
Already have an existing hourly Cost & 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).
You can link multiple AWS accounts to one AWS integration. These accounts can be either management accounts or member accounts; authentication information (IAM Role or Access Key) must be included for each linked account. Linking multiple accounts simplifies your setup process and grants access to the latest cost and right sizing reports.
Only the first account assigned to an AWS Integration (from the Data Collection tab) has the ability to send performance metrics to CloudWisdom. Additional accounts added to your integration collect only cost and right sizing data. To send performance data, create a separate AWS integration.
You can remove linked accounts from your AWS integration using the following steps:
The following best practices ensure optimal Cost & Usage report setup.
Some customers store their billing files in a shared management account and need to grant CloudWisdom restricted access to one specific S3 bucket. You can use the management 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.