Skip to content
Connection Guide

Connect Elastic Security Without Breaking the Audit Trail

Use this guide to connect Elastic Security or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeLog collection
CategoryLogging
Checklist3 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Elastic Security and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated Elastic API key with read-only Kibana and index privileges for the target space.
  2. 2
    Configure base_url and optionally space_id.
  3. 3
    Validate rules, cases, and alert search access before enabling sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

api_key

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.