Integrations
Integrations are how CloudQuery Platform connects to your cloud providers, SaaS apps, and destination databases. When you set up a sync on the platform, you’re configuring a source integration (where data comes from) and one or more destination integrations (where data goes). The platform handles the connection lifecycle, scheduling, and error handling for you.
CloudQuery brings together data from many sources through an integration-based architecture, with source, transformer and destination integrations acting as independent components.
For the full technical details on integration architecture, gRPC communication, and building custom integrations, see the CLI integration docs.
Sources Destinations
┌──────────┐ ┌──────────────────┐
│ AWS │──┐ ┌──│ S3 → ClickHouse │ (default)
├──────────┤ │ ┌──────────┐ │ ├──────────────────┤
│ GCP │──┼─│ Sync │─┘ │ S3 │
├──────────┤ │ └──────────┘ └──────────────────┘
│ Azure │──┤
├──────────┤ │
│ GitHub │──┘
├──────────┤
│ 70+ │
│ more │
└──────────┘A sync connects one or more source integrations to one or more destination integrations, forming a data pipeline. Browse all available integrations on the CloudQuery Hub.
Source Integrations
Source integrations connect to your cloud providers, SaaS applications, and APIs to extract configuration and asset data. Each source integration:
- Defines the schema (tables) for the resources it syncs.
- Authenticates with the supported API, SaaS service and/or cloud provider.
- Extracts data from the supported APIs and transforms them into the defined schema.
- Sends the data for further processing by the rest of the pipeline.
Browse Source Integrations
Browse the 70+ source integrations supported by the platform below. Full configuration reference and supported tables for each integration live on the CloudQuery Hub. You can jump directly to any integration below, or see the Integration Directory for a complete organized listing.
Cloud Infrastructure
| Integration | Hub Docs |
|---|---|
| AWS | Docs |
| AWS Cost & Usage Reports | Docs |
| GCP | Docs |
| Azure | Docs |
| Kubernetes | Docs |
| Oracle Cloud | Docs |
| DigitalOcean | Docs |
Security & Identity
| Integration | Hub Docs |
|---|---|
| Okta | Docs |
| Entra ID | Docs |
| CrowdStrike | Docs |
| SentinelOne | Docs |
| Wiz | Docs |
| Palo Alto Cortex | Docs |
| Snyk | Docs |
| Cloudflare | Docs |
Engineering & DevOps
| Integration | Hub Docs |
|---|---|
| GitHub | Docs |
| GitLab | Docs |
| Backstage | Docs |
| Datadog | Docs |
| PagerDuty | Docs |
Browse all 70+ source integrations →
Setting Up Source Integrations
The platform provides guided setup for the most popular integrations:
- AWS (Guided Setup): automated IAM role creation with CloudFormation
- AWS (Manual Setup): manual IAM role configuration
- GCP: service account and organization-wide access
- Azure: service principal configuration
- GitHub: personal access token setup
- Kubernetes: cluster access via kubeconfig
For any integration not listed above, use the General Integration Setup Guide to configure it with YAML.
Destinations
Destination integrations receive data from source integrations and write it to a database, data warehouse, message queue, or file storage system.
Default Destination: S3 → ClickHouse
When you create a sync on CloudQuery Platform, data is first written to S3 and then processed through a data pipeline into the built-in ClickHouse database. This powers platform features like the Asset Inventory, SQL Console, Policies, and Reports.
Additional Destinations
You can also sync data to additional destinations alongside the default ClickHouse destination. To set up a new destination, see the General Destination Setup Guide. Popular additional destinations include PostgreSQL, BigQuery, and Snowflake.
Platform features like Asset Inventory and SQL Console depend on the default ClickHouse destination. Additional destinations serve as auxiliary targets for your data.
Transformers
Transformers are available only with the CloudQuery CLI
Transformers are optional components that sit in between the source and destination. They allow you to modify data before it is written to the database, such as modifying the table name, obfuscating secrets, or adding additional columns. See the CLI transformer docs for configuration details and available transformers.
Using the CLI instead? See CLI Integrations for the self-hosted configuration reference and architecture details.
Next Steps
- Syncs - how the platform manages syncs, write modes, and table views
- Setting up a sync - configure your first sync on the platform
- Quickstart - end-to-end walkthrough from account creation to querying data
- Integration guides - step-by-step setup for AWS, GCP, Azure, GitHub, Kubernetes, and more
- General integration setup guide - add any source integration to the platform
- General destination setup guide - add a custom destination beyond the default ClickHouse
- Browse source integrations - find integrations for your cloud providers and SaaS apps