Legacy CUR creates a CFN for all the other resources you will need to query using Athena. Standard export (CUR 2.0) does not seem to create a CFN for you... why is that?
Hey, so i spoke to Zach you are right - it doesn't have a feature to deliver a CFN template that can be used to setup Athena. BUT if you can comment on here your company name i can add you to the feature request for this! The workaround: This means you need to set it up "manually", but fortunately this is quite easy to do with AWS Glue: Create an export of CUR 2.0 in the Parquet format and with the overwrite file delivery preference. (Athena has some benefits with Parquet and overwrite is required so that data doesn't appear twice in Athena). In Athena, use the notebook editor with Trino SQL and click "Create" to create a table with "AWS Glue Crawler". Using the Glue crawler workflow, point the glue crawler to run on the s3://///data folder to automatically load all of the delivered partitions for the specified export to Athena After the glue crawler is complete, you can use Athena to write queries on the table created by the glue crawler.
![ILLSLICK - KILLSHOT REMIX [FULL VERSION]](http://i.ytimg.com/vi/RIK8RrqIAzE/mqdefault.jpg)
Legacy CUR creates a CFN for all the other resources you will need to query using Athena. Standard export (CUR 2.0) does not seem to create a CFN for you... why is that?
Hey, so i spoke to Zach you are right - it doesn't have a feature to deliver a CFN template that can be used to setup Athena. BUT if you can comment on here your company name i can add you to the feature request for this!
The workaround:
This means you need to set it up "manually", but fortunately this is quite easy to do with AWS Glue:
Create an export of CUR 2.0 in the Parquet format and with the overwrite file delivery preference. (Athena has some benefits with Parquet and overwrite is required so that data doesn't appear twice in Athena).
In Athena, use the notebook editor with Trino SQL and click "Create" to create a table with "AWS Glue Crawler". Using the Glue crawler workflow, point the glue crawler to run on the s3://///data folder to automatically load all of the delivered partitions for the specified export to Athena
After the glue crawler is complete, you can use Athena to write queries on the table created by the glue crawler.
Definitely two "point" 0
agree!