Skip to main content

CUR 2.0

AWS recommends Cost and Usage Report 2.0 (CUR 2.0) as the new way to receive detailed AWS cost and usage data. For the differences between CUR 2.0 and Legacy CUR (CUR 1.0), see Migrating from CUR to Data Exports CUR 2.0.

Support in DoiT​

Starting June 2026, DoiT platform defaults to CUR 2.0 when onboarding new AWS accounts. Existing accounts currently using CUR 1.0 are expected to be fully migrated by July 1, 2026:

  • If you're on a DoiT reseller payer account, your DoiT Account Manager will communicate with you about the migration.

  • Cloud Intelligence standalone customers and PartnerOps end customers can either grant DoiT a one-time permission ("bcm-data-exports:ListExports", "bcm-data-exports:GetExport") or run the upgrade via the DoiT console.

Upgrade via the DoiT console​

We recommend performing the upgrade after the previous month’s billing data is finalized to avoid affecting the monthly reconciliation work.

Prerequisites​

Run the upgrade​

  1. In the DoiT console, select Data ingestion and integrations > Integrations from the top navigation mega menu.

  2. On the Amazon Web Services integration card, select Assets.

  3. Locate the AWS account of interest, select the kebab menu (⋮) at the rightmost end of the entry, and select Upgrade to CUR 2.0.

    Upgrade to CUR 2.0

  4. Review the information in the upgrade dialog.

    CUR 2.0 upgrade dialog

  5. Copy the permission block and add it to the DoiT role on your AWS management account (MPA) in the AWS console.

    {
      "Effect": "Allow",
      "Action": [
        "bcm-data-exports:ListExports",
        "bcm-data-exports:GetExport"
      ],
      "Resource": "*"
    }

    These permissions allow the DoiT console to discover and read CUR 2.0 exports in your account.

  6. Select Upgrade to CUR 2.0.

    DoiT will start validating your IAM permissions and discovering CUR 2.0 exports in your account.

If the upgrade is successful, billing data from CUR 2.0 will be pulled at the beginning of the next billing month.

Contact support if validation continues to fail, if no billing data appears after the expected AWS export delay, or if you see discrepancies in billing data after migration.

FAQ​

Do I need to migrate to CUR 2.0?​

For new AWS accounts, CUR 2.0 is the default option. For existing accounts, migration is encouraged so you can benefit from improved billing accuracy and access to newer AWS billing capabilities.

Will my historical billing data change?​

No. Historical data remains available. The migration changes the source format for newly delivered billing data.

Will my reports, budgets, and alerts still work?​

Yes. DoiT continues to normalize billing data so that your existing reporting and monitoring workflows remain intact.

Can I use the same S3 bucket?​

In most cases, yes. A separate path or prefix may be used for the CUR 2.0 export, depending on how your AWS environment is configured.

Each AWS management payer account can have only one billing export path at a time. If you manage multiple payer accounts, some can remain on CUR 1.0 while others use CUR 2.0 during your transition.

Are all AWS regions and partitions supported?​

Availability of AWS Data Exports depends on AWS. Some partitions may continue using legacy CUR where CUR 2.0 is not available.

Can I move back to CUR 1.0 later?​

Though DoiT still supports CUR 1.0, moving back is not recommended because AWS has stopped building new features on CUR 1.0 and will not fix known accuracy issues.

Last updated on