Configure the Cost and Usage Report in AWS

CloudCheckr has integrated the CUR, AWS's next-generation billing tool, into our application.

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

AWS plans to deprecate the Detailed Billing Report (DBR) and will soon replace it with the CUR. CloudCheckr currently supports the DBR and the CUR. For more information, review the Transition from DBR to CUR FAQ.

Prerequisite

You must enable at least one Cost Allocation tag in AWS before you can configure the CUR in AWS.


Procedure

Follow the steps in this workflow to configure the CUR in AWS:

  1. Log in to the AWS Management Console.
  2. From the menu bar, click your account name, and select My Billing Dashboard.
    The Billing & Cost Management Dashboard opens.
  3. From the dashboard, click Cost & Usage Reports.

    The AWS Cost and Usage Reports page opens.

  4. Click Create report.

    The Report content page opens.

  5. Type a report name.
  6. Select the Include resource IDs checkbox, so that your report will include all the IDs from your individual resources.
  7. Notice that the Automatically refresh your Cost & Usage Report... checkbox is selected by default.

    This option allows AWS to refresh the CUR and upload a new report to your S3 bucket any time it detects billing charges from closed months.

    Here is an example of what your screen will look like after you complete this page:

  1. On the bottom of the Report content page, click Next.

    The Delivery options page opens.

  2. Click Configure.

    The Configure S3 Bucket wizard opens.

  3. Select an existing S3 bucket or create an S3 bucket—making sure to select a region for this new bucket.
  4. Click Next.

    The Verify Policy page of the wizard opens.

    AWS provides you with the default S3 bucket policy:

    Since this policy contains all the permissions you need to access and write the CUR files to the S3 bucket, you don't need to edit it.
  5. Select the I have confirmed that this policy is correct checkbox and click Save.
  1. On the Delivery options page, go to the Report path prefix field, and:
    1. Leave the field blank to use the default report prefix: /report-name/date-range/
    2. Include a folder name to create a separate location to store the CUR if the DBR and CUR use the same S3 bucket: folder name/report-name/
      Using the same S3 bucket for the CUR and DBR may reduce the time it takes to configure permissions, but you can use separate S3 buckets if you want.
  2. Under Time granularity, select hourly so that your CUR gets updated multiple times a day.
  3. Under Report versioning, select whether you want AWS to overwrite the previous version or deliver a new report.
  4. Under Enable report data integration for, select Amazon Redshift as your resource.

    This is where AWS will upload your CUR data for further analysis.

  5. Notice that AWS automatically selects GZIP as your compression type and CSV/TXT as your file format.
    You cannot edit the compression type or file format.

    Here is an example of what your screen will look like after you complete the Delivery options page:

  1. On the bottom of the Delivery options page, click Next.

    The Review page opens.

  2. Under Report content, make sure, at a minimum, that you:
    • included Resource IDs
    • opted in for the Data Refresh settings
  3. Scroll down to the Delivery options and make sure, at a minimum, that you selected:
    • hourly as the time granularity
    • Redshift for data integration
    • GZIP for compression type
    • text/csv for file format
  4. Once you are satisfied with your settings, click Review and Complete.

    A message indicates that AWS successfully created the CUR and will deliver it to your S3 bucket within the next 24 hours.

    Your new report is also included in the list.

If you are onboarding your AWS account using the CUR, continue to the next step: Configure the Cost and Usage Report in CloudCheckr.

How did we do?