CUR 2.0 Migration

Overview

Umbrella now supports CUR 2.0 for AWS accounts. Migrating an account from Legacy CUR to CUR 2.0 unlocks deeper AI usage visibility and a growing set of filters you can use across the platform. The migration is done from the Cloud Accounts page and takes a few minutes.

Why migrate to CUR 2.0

CUR 2.0 is a format that provides for detailed cost and usage data, delivered through AWS Data Exports. AWS continues to add new data options to CUR 2.0, so migrating keeps your account on the structure that gets new capabilities first.

After migrating, you gain:

  • Extra AI data - The AI section shows additional detail about your AWS AI usage, down to the end-user level, so you can see who is driving AI spend.
  • More filters across the platform - New CUR 2.0-based filters become available throughout Umbrella, including Cost Explorer filters, Business Mapping creation, budget definitions, and more. We keep adding new filters on an ongoing basis.
📘

Legacy CUR is still supported

Accounts on Legacy CUR keep working as they do today. Migrating is recommended so you can use the new capabilities as they are released.

🚧

Before you migrate

  • Migration is permanent. Once an account is migrated to CUR 2.0, it can't be reverted to Legacy CUR.
  • Historical data stays based on your Legacy CUR. CUR 2.0 data and capabilities apply from the migration onward.
  • Once the migration is complete and the CUR 2.0 export has been created, it can take up to 24 hours for the changes to be reflected in the platform, as we need to receive an SNS notification from AWS containing the updated export. You can track the process status in the relevant account row on the Cloud Accounts page.

Before you start

  • You need access to the AWS Billing and Cost Management console for the payer account.
  • Decide where the CUR 2.0 export will be delivered: the same bucket already connected to Umbrella (recommended), or a new bucket.

Migrate an account

  1. In Umbrella, go to Account > Cloud Accounts.
  2. Find the AWS account. In the Details column, click Migrate to CUR 2.0.
  3. In CUR Location, choose Same bucket or New bucket, then follow the matching section below.

Option 1: Same bucket (recommended) ✅

The CUR 2.0 export is created in the bucket already connected to this account. No IAM or SNS changes are needed.

  1. From the AWS console, navigate to the Data Exports page, and click on Create.

  2. Choose the export details as Standard data export, and CUR 2.0.

  3. In the additional export content, choose

    • Include resource IDs
    • Include caller identity (IAM principal) allocation data
    • Include capacity reservation columns and granularity.
  4. Set granularity to Hourly, and in file versioning, choose Overwrite existing data export file.

  5. Define compression type to Parquet.

  6. Select the same S3 bucket currently used by this account and keep the existing path prefix.

    Note: You can find the bucket name in Umbrella in the Settings > Cloud Accounts page, under the Details column.

  7. Return to Umbrella and click Migrate to CUR 2.0.
    Note: This step is optional; we validate the export type automatically once we receive the next SNS and update the account export type accordingly.

Option 2: New bucket

CUR 2.0 is delivered to a different S3 bucket you own. This requires an IAM policy update and an SNS topic on the bucket.

  1. Create the CUR 2.0 export in AWS using steps 1-5 from Option 1, and select your new S3 bucket as the destination.
  2. In New Bucket Configuration, fill in the fields:
FieldWhat it is
New Bucket NameThe S3 bucket that receives the CUR 2.0 export.
Bucket RegionThe AWS region where the new bucket is located.
  1. In Provide Access to the New Bucket, click Download JSON Files, then copy the displayed commands. This downloads the files required to update the bucket policy with read access to the new bucket and create the SNS topic.
  2. Sign in to the AWS Console in the account where the S3 bucket is located.
  3. Open CloudShell, click Actions, and upload the files downloaded in Step 4.
  4. Paste and run the commands copied in Step 4.
  5. Return to Umbrella and click Verify Access. Umbrella verifies that it can read the new bucket. T
    Note: the Migrate to CUR 2.0 button is enabled only after verification succeeds.
  6. Click Migrate to CUR 2.0 to complete the migration.
🚧

Run both commands before verifying

Verification will fail if either the bucket notification or the bucket policy update is missing. Run both commands in the AWS account that owns the bucket, then click Verify Access again.

If you need further assistance, contact our support team [email protected]


Did this page help you?