Why this matters

CUR 2.0 is generally available and on by default, so every AWS connection you make now starts with the richest billing data AWS offers.

That richness is important. CUR 2.0 carries AWS caller identity, which is what puts Bedrock and other AI spend on the role that drove it instead of leaving it as one number in your bill. It also populates AWS Account Name automatically. Both of those are yours the moment the connection is live.

Getting there is a single step now. New orgs connect CUR 2.0 directly and see their first allocated view. Teams already running CUR 1.0 move over with one click, with account ID, role ARN, bucket, and prefix carried across for you.

Your history comes with you. CUR 1.0 data stays exactly where it is, CUR 2.0 picks up from the activation month, and the two connections stay linked in the UI so the full picture is always one click away.

What we built

Three changes.

Net-new orgs connect CUR 2.0 directly. A fresh CUR 2.0 setup stands on its own, so linking an AWS account and getting the data you want is the same step.

Any CUR 1.0 connection now has a Migrate to CUR 2.0 button on its detail flyout. Click it and the CUR 2.0 setup form opens prefilled with the account ID, role ARN, bucket, and prefix pulled from the connection you already have. Everything is filled in and ready to confirm.

Migrated connections are linked in both directions. The CUR 1.0 side shows Migrated to, pointing at its CUR 2.0 pair. The CUR 2.0 side shows Migrated from, pointing back. Click through either way, so six months from now you can still tell at a glance which connection replaced which.

How it works

Starting fresh: go to Settings > Cloud Connections > AWS > Manual Setup and connect CUR 2.0.

Already on CUR 1.0: open the connection’s detail flyout and choose Migrate to CUR 2.0. Your CUR 1.0 history stays intact, CUR 2.0 picks up from the activation month, and there is no overlap to reconcile or re-drop to manage. You keep everything you have and gain the caller identity and account name data on top of it.

See it in the docs