Skip to content

Coralogix

Query Coralogix logs, metrics and traces during investigations.

View on GitHub

by Coralogix · version 2.0.1
Partner-managed Telemetry

Before you connect, choose your Coralogix region and either OAuth sign-in or a personal or team API key. If your Coralogix team uses IP access allowlisting, you must add the AWS DevOps Agent source IP addresses for your Agent Space's Region to the allowlist; see section 3. If you want Coralogix alerts to open investigations, also do step 4 after you connect.

1. Find your region

Select the label matching your Coralogix domain when you connect. A key works only in its own region.

Coralogix domain Label Hosted in
eu1.coralogix.com EU1 AWS eu-west-1 (Ireland)
eu2.coralogix.com EU2 AWS eu-north-1 (Stockholm)
us1.coralogix.com US1 AWS us-east-2 (Ohio)
us2.coralogix.com US2 AWS us-west-2 (Oregon)
us3.coralogix.com US3 Google Cloud us-central1 (Iowa)
ap1.coralogix.com AP1 AWS ap-south-1 (Mumbai)
ap2.coralogix.com AP2 AWS ap-southeast-1 (Singapore)
ap3.coralogix.com AP3 AWS ap-southeast-3 (Jakarta)

2. Choose how to authenticate

OAuth sign-in

Select OAuth in the DevOps Agent connection form, then sign in to Coralogix for the region you selected and approve the requested access. DevOps Agent completes the OAuth flow; you do not need to create or paste an OAuth client secret.

The Coralogix user who signs in needs access to the applications and subsystems the agent should investigate. Use a least-privilege, read-only role such as DataQuerying. Do not use a shared administrator account.

Personal or team API key

  1. In Coralogix, go to Settings > API Keys.
  2. Select + Add Key, choose Personal Key or Team Key, and name it, for example aws-devops-agent.
  3. In Role Presets, select the presets required by the tools you want to use. DataQuerying gives read-only query access to logs, metrics, spans, and datasets.
  4. Select Create and copy the key.

When you connect, paste the key by itself into Personal or team API key. DevOps Agent adds the Bearer prefix.

Use a personal or team key, not a Send-Your-Data (ingestion) key. A personal key works within the permissions and data scopes of the user who creates it; a team key uses the permissions configured for that key. Grant only the permissions and data access needed for the applications and subsystems you want investigated.

Ensure the API key has the permissions required by the tools you want to use. For example, to use the Alerts tools, select Alerts in Role Presets.

3. Configure network access

If your Coralogix team has IP access allowlisting enabled, add the AWS DevOps Agent public source IP addresses for the AWS Region hosting your Agent Space before connecting. Otherwise, DevOps Agent cannot reach the Coralogix MCP endpoint.

Use the complete regional list in the AWS DevOps Agent network connectivity documentation, rather than allowlisting only an individual IP observed in a request. In Coralogix, manage these entries in Settings > Login access policy > IP access; see Login access policy.

4. Trigger investigations from alerts

To automatically start an AWS DevOps Agent investigation when a Coralogix alert fires, use the webhook URL, API key, and request body that AWS DevOps Agent provides for your Agent Space.

Configure one Coralogix delivery path:

  • Notification Center (recommended): Go to Integrations > Notification Center > Connectors and create a Generic HTTPS connector that sends a POST request to the Agent Space webhook URL. Add Content-Type: application/json and Authorization: Bearer <Webhook-API-Key> headers. Then go to Integrations > Notification Center > Presets, select Alert, and create a preset with the AWS DevOps Agent request body.
  • Legacy outbound webhook: Go to Integrations > Outbound Webhooks and create a Generic outbound webhook with the same URL, headers, and request body if Notification Center is not available for your account.

For the alert, open its Response step, set Notify on to Alerts, then select the connector and preset, or the outbound webhook. Leave Notify when resolved off: this connector sends each notification as a new incident, so a recovery notification could open a second investigation. Use the request body unchanged so it follows the AWS DevOps Agent webhook format.

More in the Coralogix docs: AWS DevOps Agent, OAuth, API keys, Coralogix domain, and MCP server permissions.

Terms of Use and Data Protection

Use of the Coralogix connector for AWS DevOps Agent is subject to the Coralogix Master Subscription Terms and the Coralogix Data Processing Agreement, as updated from time to time.

By using this connector, you acknowledge and agree that:

  • AWS may collect and use metadata and usage metrics from your use of this connector, in accordance with the AWS terms applicable to AWS DevOps Agent.
  • Coralogix may notify and cooperate with AWS regarding security vulnerabilities or incidents related to this connector or affecting data processed through it.

For questions or security matters related to this connector, contact aws-devops-agent@coralogix.com.

Skills

The console offers to install these skills when you add this connector: