Send Scaleway logs to LogPulse

Scaleway Audit Trail: every change through the console, CLI, API and Terraform (IAM, API keys, Kubernetes, Instances, security groups, databases) and the sign-ins to the console.

In short
To send Scaleway logs to LogPulse, add Scaleway under Configure → Sources → Cloud. LogPulse reads the Scaleway Audit Trail API itself, without an agent. Events land in the audit, iam indexes with source scaleway and fill the Change, Authentication data models.

Overview

How Scaleway data reaches LogPulse
Vendor
Scaleway Audit Trail API
Collect
Integration pollerreads new events, maps the fields
Store
index=audit
index=iam
  1. Scaleway Audit Trail API to Integration poller
  2. Integration poller to index=audit
  3. Integration poller to index=iam

LogPulse signs in to Scaleway with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.

What you need

  • A Scaleway organization
  • An IAM application with AuditTrailReadOnly and an API key for it
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in Scaleway

Field in LogPulseWhere you find it
Organization IDIn the Scaleway console under Organization settings.
Secret keyThe secret key of an API key for an IAM application with the AuditTrailReadOnly permission set on the organization. Stored encrypted and never shown again.
Regions (optional)Leave empty for fr-par and nl-ams. Audit Trail keeps the events of each region in that region.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose Scaleway. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.

Tip: Secrets are stored encrypted and never shown again. To change one, paste a new value; the rest stays.

What arrives

Data sourceIndexSourceSourcetypeWhat it holds
Audit eventsauditscalewayscaleway:audit_trail:eventWho changed which resource in which project, with the method, address, user agent and result.
Sign-insiamscalewayscaleway:audit_trail:authenticationSign-ins to the Scaleway console: who, how, from where and whether it worked.

The index is the kind of data and the source is the product, so detection rules for that kind of data find Scaleway without changes.

Note: Create an IAM application, give it the AuditTrailReadOnly permission set on the organization and make an API key for it. The access key is not needed, only the secret key.
Note: Audit Trail covers the products that write to it; what happens inside a Kubernetes cluster (kubectl) is not in it.

Fields and data models

Data modelWhat you get
ChangeWho changed which resource, with method, project, address and result.
AuthenticationConsole sign-ins with user, method, src_ip, country and result.

Field names follow the CIM field names. These are the fields LogPulse sets on Scaleway events; a field is left out when Scaleway did not send a value.

  • action
  • app
  • authentication_method
  • dest
  • http_user_agent
  • id
  • mfa_type
  • object
  • object_category
  • object_id
  • reason
  • request_id
  • service
  • signature
  • src_country
  • src_ip
  • status
  • status_code
  • user
  • user_id
  • vendor_account
  • vendor_project
  • vendor_region

The original record of Scaleway is kept with each event under raw, so nothing the vendor sent is lost.

3. Check the data

The first events arrive within a few minutes. Check what came in:

earliest=-1h index IN (audit, iam) source IN (scaleway)
| stats count by index, source, sourcetype

The integration page in LogPulse shows when it last read events and the last error, if any.

Troubleshooting

The connection test names what is wrong. These are the answers you are most likely to see.

What you seeWhat to do
Scaleway refused the secret key. Check that the API key still exists.Create a new API key for the IAM application and paste its secret key, not the access key (SCW…).
The API key may not read Audit Trail. Give its IAM application the AuditTrailReadOnly permission set on the organization.In IAM, add a policy to the application with AuditTrailReadOnly, scoped to the organization (not to one project).
regions are fr-par, nl-ams or pl-waw, separated by commasLeave the field empty for fr-par and nl-ams, or list only the regions you use.
The test passes but no events arrive.Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Scaleway may also simply have had nothing new.

Frequently asked questions

How do I send Scaleway logs to LogPulse?
Add the Scaleway cloud integration under Configure, Sources, Cloud in LogPulse and fill in Organization ID, Secret key. LogPulse reads the Scaleway Audit Trail API itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in Scaleway?
A Scaleway organization. An IAM application with AuditTrailReadOnly and an API key for it. Read access is enough for collecting logs.
Which index does Scaleway data go to?
The index is the kind of data: audit, iam. The source is the product: scaleway. Each data source has its own sourcetype, listed on this page.
Which data models does Scaleway fill?
Change, Authentication. Detection rules and dashboards written for a data model work on Scaleway without changes.