We use tracking cookies to understand how you use the product and help us improve it. Please accept cookies to help us improve. You can always opt out later via the link in the footer.
Non-invasive account access for better security and efficiency.
Import data with CloudQuery SDKs and build your own plugins.
Query cloud assets and security with a simple SQL-based UI.
To install CloudQuery, run the following command in your terminal:
brew install cloudquery/tap/cloudquery
Next, run the following command to initialize a sync configuration file for AWS Cost Usage Reports to S3:
cloudquery init --source=awscur --destination=s3
This will generate a config file named awscur_to_s3.yaml. Follow the instructions to fill out the necessary fields to authenticate against your own environment.
Next, log in to the CloudQuery CLI. If you have't already, you can sign up for a free account as part of this step:
cloudquery login
cloudquery sync awscur_to_s3.yaml
This will start syncing data from the AWS Cost Usage Reports API to your S3 environment! 🚀
See the CloudQuery documentation portal for more deployment guides, options and further tips.
PutObject
permissions to sync to the S3 destination and we recommend that you grant only these permissions to CloudQuery in order to keep your setup as secure as possible. CloudQuery does not require access to your S3 cloud configuration settings, only permission to add objects to your S3 buckets..aws
directory of your home folder. The two files are almost identical in format but if there is a conflict, CloudQuery will prioritise the credential information that it reads from the credentials
file over those found in config
.