Configure the Cost and Usage Report in CloudCheckr

Prerequisites:
By the end of 2019, AWS will deprecate the Detailed Billing Report (DBR) and replace it with the CUR. As a result, the CUR will become CloudCheckr's primary billing method. At this time, CloudCheckr customers can use the DBR or the CUR. For more information, review the Transition from DBR to CUR FAQ.

CloudCheckr has integrated the CUR into our application—providing more visibility into Reserved Instances (RIs), AWS Marketplace charges, and other billing features.

In this topic, you will learn how to configure the CUR in CloudCheckr.

Procedure

  1. Launch CloudCheckr.
  2. If you have already created an account in CloudCheckr, select the account where you need to configure the CUR.
  3. From the left navigation pane, choose Account Settings > Billing and Usage.

    The Billing and Usage Configuration page opens.

  4. In the Cost and Usage Report (CUR) section, provide the values that you created earlier in AWS:

    • RI collect start date
    • report name
    • bucket name
    • bucket region
    • folder prefix
      • For the folder prefix:
      • If you did provide a report path prefix when you configured your report in AWS, copy the folder name.
      • If you did not provide a report path prefix, leave this field blank.

  5. Select the Enabled checkbox to indicate that you want the application to use the CUR.
  6. Click Save Configuration.

Error Messages

You may encounter an error message if you have provided incorrect information or no information in the Cost and Usage Report section:

This table identifies each field in the Cost and Usage Report section and shows how invalid or no information can result in an error message.

: indicates that you provided invalid or no information for that field

: indicates that you provided valid information for that field

Scenario

Region

RI Collect Start Date

Bucket Name

Report Name

Folder Prefix

Error Message

Solution

Valid region; other settings are blank
Report Name cannot be empty.

Bucket Name cannot be empty. 		Populate the blank fields.
Valid region and bucket name; other settings are blank
Report Name cannot be empty.

 Populate the blank fields.
Valid region, bucket name, and report name; other settings are blank
Unable to locate the CUR manifest file.

 Populate the blank fields.
Valid region, bucket name, report name, and RI start date; folder prefix is blank
Unable to locate the CUR manifest file.

 Populate the blank field.
Region does not support S3 API command; all other settings are configured correctly
An unexpected error occurs.

Select another region.
Region supports S3 API command, but is invalid for selected bucket; all other settings are configured correctly
Region is invalid for the given bucket.

Select a valid region for your S3 bucket.
Incorrect bucket name; all other settings are configured correctly
Region is invalid for the given bucket.

Provide a valid bucket name.
Incorrect report name; all other settings are configured correctly
Unable to locate the CUR manifest file. Provide a valid report name.
Incorrect RI Collect start date; all other settings are configured correctly
Unable to locate the CUR manifest file. Provide a valid start date.
Incorrect folder prefix; all other settings are configured correctly
Unable to locate the CUR manifest file. Provide a valid folder prefix.
Uncredentialed account; all other settings are configured correctly
There was an error trying to download the manifest file. Credential your account before you configure your CUR settings.
These errors messages are associated with credentialed accounts except where noted.

How did we do?