You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current CSV delivery format may not be suitable for this due to lack of a unique ID per row (see #30). New approach is to add a new delivery format (parquet compression for Athena import), import the new files to BigQuery, then use a SQL view to mimic the GCP billing report table.
I was not able to complete this ticket. There is currently a CUR being generated in Parquet format in AWS; I was able to connect that bucket to a BigQuery Data Transfer job, but it complains about the format of the report. The Athena export format may not be appropriate.
From #26.
AWS billing data should be loaded into BigQuery and queried in a fashion similar to how GCP billing data is queried for the GCP report.
The text was updated successfully, but these errors were encountered: