This is a legacy method for obtaining detailed reports. See Cost And Usage Reports for Amazon’s new reports. CloudWisdom recommends switching all AWS integrations to the CUR data collection method.
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.
S3 bucket nameinto the corresponding field. The bucket name is case sensitive and must exactly match the bucket created in Step 1.
The following best practices ensure optimal detailed billing setup.
Keep your billing files in a dedicated S3 bucket. Having a large number of other files in the same S3 bucket requires more API calls to locate your billing files.
Don’t write billing files from more than one AWS account into the same S3 bucket, as the filenames can be confused.
You may not have access to your billing preferences if you have purchased AWS services through a reseller. You must contact your reseller and request to be set up with an S3 bucket to store your detailed billing data.
Extracts or summaries of your billing data must have the exact same file name format and file structure of AWS detailed billing files to be ingested by CloudWisdom.
Reseller concerned about sharing an S3 bucket?
Virtana only reads the costs for accounts that we monitor; we discard all data for any unrelated accounts. You can also have them reach out to our support team with any questions they may have.