Issue Description:
Currently when we use an existing report we replace the event in the exiting CUR bucket and point it to our Lamda function which invokes the Glue crawler. This could break existing CUR Athena pipelines, and does not support an idempotent deployment. This would prevent us from having multiple working deployments.
Solution:
For existing CUR reports, The cloudformation template creates an additional CUR bucket, and we configure replication to replicate the data within the customer configured CUR bucket to into our new bucket. This workflow will allow us to delete our bucket on CFN deletion without dataloss to the customer.
Issue Description: Currently when we use an existing report we replace the event in the exiting CUR bucket and point it to our Lamda function which invokes the Glue crawler. This could break existing CUR Athena pipelines, and does not support an idempotent deployment. This would prevent us from having multiple working deployments.
Solution: For existing CUR reports, The cloudformation template creates an additional CUR bucket, and we configure replication to replicate the data within the customer configured CUR bucket to into our new bucket. This workflow will allow us to delete our bucket on CFN deletion without dataloss to the customer.