Announcement
New in Cloud Intelligence™: AWS CUR 2.0 support with an in-place upgrade path
By Herald
·Shipped by
This page is also available in Deutsch, Español, Français, Italiano, 日本語, and Português.
New AWS connections default to CUR 2.0, and existing payer accounts can switch when you're ready, without disruptions.
AWS is replacing the legacy Cost and Usage Report with CUR 2.0, built on its newer Billing and Cost Managment Data Exports framework. If you've been tracking that migration, good news: DoiT Cloud Intelligence™ now supports CUR 2.0 end to end.
We built this change as a self-serve upgrade that validates your AWS Data Exports configuration before changing anything.
- Upgrade in place: Move a payer account from Legacy CUR to CUR 2.0 with the new upgrade flow on your AWS assets page. Your existing billing data stays intact.
- Start new accounts on CUR 2.0: New AWS connections default to CUR 2.0, with your export configuration discovered and validated automatically.
- See new data fields: Capacity reservation details and IAM principal information land in your cost data, so you can see reserved-capacity usage and who is driving spend.
- Keep your resource tags: CUR 2.0 stores resource tags as JSON; they map to DoiT labels automatically, so existing filtering and attribution workflows keep working.
To get started, open your AWS assets page in the DoiT console and look for the CUR 2.0 upgrade option.
Available to Cloud Intelligence™ customers with AWS payer accounts. Legacy CUR remains fully supported.