Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Troubleshooting CUR 2.0

Some columns available in CUR are missing in CUR 2.0; where are they?

In CUR 2.0, four column types became nested into four individual columns. The resulting nested columns are: product, discount, resource_tag, and cost_category.

In legacy CUR, there could be hundreds of columns with names that started with these strings. The variations depended on customer usage of Amazon services or agreements with Amazon. This schema design resulted in hundreds of columns that were often sparsely filled. The variability of the columns could also cause problems with SQL queries due to a charging schema.

As a result, the columns that could vary across different Amazon columns were nested together into these four columns. Certain product columns that are commonly used were not nested.

You can recreate the schema of the CUR in your CUR 2.0 export by using the dot operator in SQL. To learn how to do this, see Migrating from CUR to Data Exports CUR 2.0.

What will happen to legacy Cost and Usage Reports; will it be deprecated?

We currently have no plans to deprecate legacy CUR. However, as CUR 2.0 in Data Exports offers several improvements such as a consistent schema, nested data, and additional columns (bill_payer_account_name and line_item_usage_account_name), we recommend migrating to CUR 2.0.

While there is no target date, we are planning to eventually deprecate Cost and Usage Reports under Legacy Pages in the console. However, all of the same functionality to create, update, and delete legacy CUR is available through the Data Exports console page.

Does creating an export of CUR 2.0 affect my legacy CUR?

CUR and CUR 2.0 are two distinct reports. When creating CUR 2.0, there is no impact on your existing CUR settings. You can choose between legacy CUR and CUR 2.0 based on your preferences.

I have IAM permissions to use Data Exports and the CUR table; why can’t I create an export of CUR 2.0?

Make sure you also have IAM permissions for cur:PutReportDefinition.

When attempting to create a data export with the same CSV format as the legacy CUR columns, I get an "Invalid QueryStatement" error. How can I resolve this?

Currently, you can't rename your columns to have special characters such as "/" to match the legacy CUR column names in CSV format. For information about the supported character types, see SQL query.

After migrating to Data Exports CUR 2.0, can I have a legacy CUR export and a CUR 2.0 export at the same time?

Yes, you can have up to 10 legacy CUR exports and 5 CUR 2.0 exports at the same time.

When attempting to create an export of CUR 2.0, I get the error "This account is unable to create an export against this table". Why can't I create a CUR 2.0 export?

Unlike legacy CUR, CUR 2.0 does not currently support creating an export of CUR 2.0 with pro forma billing data. If you are part of a billing group in Amazon Billing Conductor, you are only allowed to receive pro forma billing data. As a result, you receive this error message when trying to create an export of CUR 2.0. You can still create a legacy CUR export.