We recommend you migrating to CUR 2.0 as it is more performant and future proof way of getting the most detailed information about your AWS cost and usage.

For creation of CUR 2.0 export from scratch please use a CloudFormation Stack published on Cloud Intelligence Dashboard workshop. This solution can create the CUR2.0, transfer of data to a dedicated FinOps account and create needed Athena table for your analysis.

This repository provides an additional set of tools to simplify your migration to CUR 2.0.

• query-converter - Gen AI assistant for conversion of SQL queries to CUR 2.0 format. You will need a standard CUR 2.0 export with athena integration to run resulting queries.
• migrate-cur1 - A script for creation of CUR 2.O export, compatible with Legacy CUR format. Use it if you have existing integration with 3rd party tool and it was not updated to CUR 2.0 yet.
• hard_coded_query_converter.py - Coverter for CUR legacy Queries to CUR 2.0 not using AI. Mainly for customer who cannot use Bedrock becasue of restrictions.

This repository provides a ready to use command line tool query-converter. You can use it to transform your Legacy CUR queries to CUR2.0 format using Amazon Bedrock. This tool uses 'claude-3-sonnet' model extended with additional awareness about the specifics of CUR1 to CUR2.0 transformation.

Please make sure you have the model anthropic.claude-3-sonnet-20240229-v1:0 activated in Amazon Bedrock console.

1. Open CloudShell in us-east-1 region.
2. Run following command:

pip3 install -U git+https://github.com/aws-samples/aws-data-exports-setup

Run the interactive prompt, and insert your CUR1 queries

query-converter

The tool also can read GitHub public urls.

You can try to rerun the same query coveter explaining additionally if there was an issue. Please note that this tool does not save the history of the conversation so you need to provide query again. Also you can enter r or retry to retry the same request again. Some times it helps.

This tool detects currently deployed legacy CUR, reads the file to define a format, produces a query that is equivalent to your legacy CUR data export and creates the new CUR 2.0 to the same bucket.

1. Select existing Legacy CUR (Only Athena and Parquet format are supported)
2. Get the latest Parquet file and analyze the schema
3. Create CUR 2.0 Query which will have the same schema as legacy.
4. Update current CUR bucket policy
5. Create the new CUR 2.0

1. Open CloudShell in us-east-1 region.
2. Run following command:

pip3 install -U git+https://github.com/aws-samples/aws-data-exports-setup

Run migration script

migrate-cur1

The tool will suggest the choice of initial Legacy CUR.

See CONTRIBUTING for more information.

This library is licensed under the MIT-0 License. See the LICENSE file.