CloudQuery
Connect CloudQuery to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your CloudQuery connection as infrastructure evidence.
| Category | Infrastructure |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In CloudQuery:
- Sign in to the CloudQuery Platform (https://cloud.cloudquery.io) and create a team if you do not have one.
- Click Team Settings in the left sidebar and select the API Keys tab.
- Click Generate new key.
- Enter a key name, select the scope Read and write (needed for the CloudQuery REST API; Syncs operations only only runs syncs), choose an expiration, then click Generate new key.
- Copy the key and store it securely; you will not be able to see it again.
Where to find the other values:
- Account / Org / Workspace (optional): The team you select in the CloudQuery Platform; the key is created under that team's Team Settings.
CloudQuery shows the secret only once, so copy it before you leave the page.
CloudQuery documents only two scopes: 'Syncs operations only' and 'Read and write'; there is no read-only API scope, so REST API access requires 'Read and write'. The API base URL is not stated on this page.
Source: cloudquery.io, checked 2026-10-07.
-
On Compliance › Connectors, open CloudQuery, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) - Account / Org / Workspace (optional) - -
Click Connect with token.
Frameworks
No automated compliance test reads CloudQuery, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Infrastructure connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks