Skip to main content
Connect your Redis instance so Myrmex can audit its hardening and compliance, check its operational health, explore its keyspaces, and — with approval — run commands for you. Myrmex reaches the instance over the Redis protocol (RESP) 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 memory usage, evictions, connected clients, and persistence status.

Explore keyspaces

Review keyspaces and key patterns so you can see what the instance holds.

Describe structure

Inspect key types, sizes, and TTLs.

Sensitive-data scan

Scan keys and values for personal or sensitive data that needs protection.

Run commands

Execute read commands any time; write commands require your confirmation.

​
Before You Start

  • A Collector on a network that can reach the Redis host on its TCP port (default 6379). See Collector mode.
  • An AUTH password set on the instance (configure it in Step 1). This connector authenticates with a password only (the Redis default user); it does not use ACL usernames.

​
Step 1 — Set the Credential in Redis

Set an AUTH password so Myrmex authenticates as the default user. The audit reads server settings through INFO and CONFIG GET (read-only).
Always require AUTH and keep the instance off the public network. The posture audit checks settings such as protected-mode, bind, requirepass, and dangerous or renamed commands.

​
Step 2 — Add the Integration in Myrmex

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

​
Connect

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

​
Notes

  • Read-only in practice. Auditing, health, exploration, and sensitive-data scans only read state. Write commands run through Run commands require your confirmation.
  • Nothing is stored. Every operation runs in real time through the Collector; results return to your Workspace and no instance data is retained on the Myrmex side.
  • Authentication. The connector uses password-only AUTH (the Redis default user); named ACL users are not used here.