-
Spike
-
Resolution: Done
-
Major
-
None
-
None
-
15
-
False
-
None
-
False
-
-
AWS introduced CUR 2.0 which collapses some columns into a new column with key-value pairs of the collapsed columns. We should investigate the impact here to mitigate disruption in processing customer data.
For example in CUR 2.0, product/operatingSystem and product/memory columns would be rolled into key/value pairs in a new product column.
Here are some relevant links:
- Current CUR columns: https://docs.aws.amazon.com/cur/latest/userguide/data-dictionary.html
- CUR 2.0 columns: https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur2.html
Customers could create a CUR 2.0 report that is backwards compatible with CUR according to this article, https://aws.amazon.com/blogs/aws-cloud-financial-management/introducing-data-exports-for-billing-and-cost-management/
- is cloned by
-
COST-5052 AWS - Add support for V2 data exports
- New
1.
|
Create new 2.0 report in dev account | Closed | Luke Couzens | ||
2.
|
Update nise to support AWS v2 CUR | Closed | Unassigned | ||
3.
|
Update the integrations wizard to handle legacy reports | Closed | Luke Couzens |