Connecting Coralogix to Landfall
Landfall reads your telemetry through a single Coralogix API key, nothing more. How you get logs and events into Coralogix in the first place (CloudWatch, CloudTrail, an agent, whatever) is entirely between you and Coralogix; this guide covers the two steps on Landfall's side: creating a key scoped for the job, and pasting it in.
What you'll need
- A Coralogix account, and to know which region domain your team logs in with (shown at sign-in: eu1/eu2/us1/us2/ap1/ap2/ap3).
- An admin on your Landfall organization, to save the connection under Settings → Integrations.
1. Create a Coralogix API key
Landfall only ever reads from Coralogix: it verifies the key is alive and then queries your logs when an incident is being investigated. Give it a key scoped to match: a Team key with the Actions and DataQuerying role presets, not a broader admin key. Actions alone is enough for the connection test below to pass, but the investigator agent needs DataQuerying too. Without it, log queries fail with a permissions error even though the integration shows as connected.
Coralogix → Settings → API Keys
Open the API Keys page and click Add key.
coralogix.com/settings/api-keys
Key type: Team · Role presets: Actions + DataQuerying
Name it something you'll recognize later (e.g. landfall-integration), set Key type to Team Key, and pick both Actions and DataQuerying from Role Presets, the narrowest combination that covers Landfall's connection check and its actual log queries. Neither preset alone is sufficient.
coralogix.com/settings/api-keys · Add key
Role Presets accepts more than one: select Actions, then add DataQuerying the same way. Copy the value
Coralogix shows the raw key exactly once. Copy it now: you'll paste it straight into Landfall in the next step, and it won't be shown again.
coralogix.com/settings/api-keys
2. Add it to Landfall
In Landfall, open Settings → Integrations → Coralogix for your organization. It asks for exactly two things: the key you just created, and your region domain.
Paste the key, select your region domain, and Test connection
Settings → Integrations → Coralogix
A successful test reads "Coralogix API key valid (<your-domain>)". Save integration
Settings → Integrations
Coralogix now shows Configured alongside your organization's other connectors.
- Double check the region domain matches exactly what you log into Coralogix with; a mismatched region is the most common cause.
- Confirm the key is enabled and hasn't been rotated or deleted since you copied it.
- The key needs the Actions role preset (or equivalent read access); a Send Your Data-only key will be rejected.
- The connection test above only checks Actions. It doesn't exercise a log query. If the key is missing DataQuerying, Coralogix rejects every query with a permissions error even though the integration shows Configured.
- Edit the key in Coralogix (Settings → API Keys) and add the DataQuerying role preset. No need to create a new key or reconnect in Landfall, the existing key value keeps working.
Reference
| Field | Value |
|---|---|
| API key | A Coralogix API key, sent as Authorization: Bearer |
| Required role presets | Actions (connection check) + DataQuerying (log queries) |
| Region domain | coralogix.com · eu2.coralogix.com · coralogix.us · cx498.coralogix.com · coralogix.in · coralogixsg.com · ap3.coralogix.com |