Scaleway

Connect Scaleway to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Scaleway:

   1. In the Scaleway console, click IAM & API keys on the top-right drop-down menu, select the Applications tab and click Create application. Enter a name (and optional description) and click Create application.
   2. Back in IAM & API keys, click the API keys tab and click + Generate API key.
   3. Select the bearer of the key: choose the IAM application you just created.
   4. Choose an expiration (Never, 1 hour / week / month / year, or Custom).
   5. For the Object Storage question, choose No, skip for now, then click Generate API key.
   6. Copy the secret key from the next screen: this is your only chance to save it.
   7. In the side menu, click IAM, open the Policies tab and click Create policy.
   8. Enter a name, and select the application as the principal.
   9. Add a rule: select the permission sets the application needs, choose the scope (All projects or Specific projects), and click Confirm rule. Click Add new rule to add another rule if needed.
   10. Click Create policy.

   Scaleway shows the secret only once, so copy it before you leave the page.

   Scaleway's public documentation does not cover every step.

   scaleway.com/en/docs returned 403 to automated reads, so the steps were read from Scaleway's own docs source repository (github.com/scaleway/docs-content), which publishes that site. An API key inherits its bearer's permissions, so the application's policy is what keeps it read-only. The Organization ID is on the Organization Settings page (Scaleway's docs describe a Copy ID button next to the Organization name), but that page was not read directly here. Verification: the policy page does not name read-only permission sets (IAMReadOnly, InstancesReadOnly were removed), so which sets to pick is left open. The fourth source was not fetched (three-source limit).

   Source: raw.githubusercontent.com, raw.githubusercontent.com, raw.githubusercontent.com, scaleway.com, checked 2026-10-07.

   The permissions Safeguard needs: IAMReadOnly, InstancesReadOnly.

2. On Compliance › Connectors, open Scaleway, click Connect, choose API token and fill in:

   Field	What to enter
   Secret key	Required. Stored encrypted and never shown again.
   Organization ID	Required.
   Zones (optional)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Scaleway and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Cloud 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