Skip to main content
Connect your Elasticsearch cluster so Myrmex can audit its hardening and compliance, check its operational health, explore its indices, and — with approval — run queries for you. Myrmex reaches the cluster over its REST API through a Collector on your network. Operations run live and on demand through the Integration Specialist agent — Myrmex reads only what you ask for and keeps none of your data on the Myrmex side.

​
What Myrmex Can Do

Compliance audit

Run a Security Posture audit and map findings to CIS, ISO 27001, NIST CSF, and BACEN frameworks.

Health checks

Review cluster health, shard allocation, and node resource use.

Explore indices

List indices so you can see what the cluster holds.

Describe structure

Inspect an index’s mappings, settings, and shards.

Sensitive-data scan

Scan indices and fields for personal or sensitive data that needs protection.

Run queries

Run read queries any time; write operations require your confirmation.

​
Before You Start

  • A Collector on a network that can reach the Elasticsearch host on its HTTP port (default 9200). See Collector mode.
  • A dedicated user for Myrmex (create it in Step 1).
  • TLS is recommended. Set Protocol to https where the cluster is TLS-enabled.

​
Step 1 — Create the Credential in Elasticsearch

Create a dedicated, least-privilege role and user for auditing. Cluster monitor and read_security cover health, settings, and security configuration; view_index_metadata exposes index settings and mappings. Run the calls below (via the Dev Tools console or the REST API).
Keep the role read-only for auditing. Add read on the target indices only if you want the agents to query documents, and grant write privileges only for confirmation-gated Run queries operations.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Elasticsearch, then fill in:

​
Connect

Click Connect to validate the login and protocol. The cluster then appears under Environment → Integrations alongside your other integrations, and you can start asking the AI about it in the Workspace.

​
Notes

  • Read-only by default. Auditing, health, exploration, and sensitive-data scans only need the read-only role above. Add write privileges only if you want confirmation-gated Run queries operations.
  • Nothing is stored. Every operation runs in real time through the Collector; results return to your Workspace and no cluster data is retained on the Myrmex side.
  • TLS. Prefer https; the posture audit flags a cluster served over plain http.