More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Elasticsearch Config Check

    1

    Check elasticsearch.yml, kibana.yml, opensearch.yml, opensearch_dashboards.yml and Compose services for security off on reachable nodes, passwords in files, OpenSearch demo certificates, open CORS and missing HTTPS.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Elasticsearch Config Check

    Elasticsearch Config Check

    Example session with this skill installed

    Check this project with elasticsearch-config-check.

    • Read your context and instructions
    • Compiled the elasticsearch config check

    $ python3 scripts/check_elastic.py examples/risky
    BLOCK config/elasticsearch.yml:23 E03 PASSWORD_IN_CONFIG
    xpack.security.authc.realms.ldap.corp.bind_password=<redacted, 22 chars>
    Why: A password, token or client secret is written in the config file or the Compose environment (elasticsearch.password, opensearch.password, ELASTIC_PASSWORD, bind_password, keystore passwords, a password inside a host URL). Everyone with the repository or a copy of the file can log in with it, and it stays in git history after you remove it.
    Safer: Change the password, then keep it out of the file: use the keystore (elasticsearch-keystore, kibana-keystore, opensearch-keystore), a ${VARIABLE} reference, or a *_FILE secret such as ELASTIC_PASSWORD_FILE.

    BLOCK config/kibana.yml:6 E03 PASSWORD_IN_CONFIG
    BLOCK docker-compose.yml:7 E01 ELASTIC_SECURITY_OFF_ON_NETWORK
    BLOCK docker-compose.yml:28 E02 OPENSEARCH_SECURITY_OFF_ON_NETWORK
    BLOCK opensearch/opensearch.yml:16 E04 OPENSEARCH_DEMO_SECURITY_ON_NETWORK
    BLOCK opensearch/opensearch_dashboards.yml:5 E03 PASSWORD_IN_CONFIG
    REVIEW config/elasticsearch.yml:13 E14 CERTIFICATE_CHECK_OFF
    REVIEW config/elasticsearch.yml:16 E13 TLS_OFF_ON_NETWORK
    REVIEW config/elasticsearch.yml:17 E17 ANONYMOUS_ACCESS
    REVIEW config/elasticsearch.yml:27 E12 CORS_ANY_ORIGIN
    REVIEW config/elasticsearch.yml:30 E16 WILDCARD_DELETE_ALLOWED
    REVIEW config/kibana.yml:2 E13 TLS_OFF_ON_NETWORK
    REVIEW config/kibana.yml:7 E14 CERTIFICATE_CHECK_OFF
    REVIEW config/kibana.yml:8 E15 ENCRYPTION_KEY_IN_FILE
    REVIEW dev/opensearch.yml:4 E11 SECURITY_OFF_LOCAL
    REVIEW docker-compose.yml:18 E15 ENCRYPTION_KEY_IN_FILE
    REVIEW docker-compose.yml:20 E13 TLS_OFF_ON_NETWORK
    REVIEW legacy/elasticsearch.yml:5 E18 SECURITY_NOT_SET
    REVIEW opensearch/opensearch_dashboards.yml:3 E14 CERTIFICATE_CHECK_OFF

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 7 files, 7 with Elasticsearch/OpenSearch content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    BLOCK docker-compose.yml

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A tutorial docker-compose.yml with xpack.security.enabled=false and ports "9200:9200" puts every index on the internet without a password, and Docker's published ports skip most host firewalls. Bots find clusters like that within hours and leave a ransom note where the data was. An OpenSearch container started without DISABLE_INSTALL_DEMO_CONFIG=true is just as open in a quieter way: it runs the demo certificates, whose private keys are public, and demo users with well-known passwords. This skill finds those and ten other Elasticsearch, Kibana and OpenSearch setting mistakes before the cluster goes live, and tells you how to fix each one.

    Your agent runs a scanner on your project: elasticsearch.yml, kibana.yml, opensearch.yml and opensearch_dashboards.yml (and named variants such as elasticsearch-node1.yml), plus Docker Compose services that run the official Elasticsearch, Kibana, OpenSearch and OpenSearch Dashboards images. Flat dotted keys and nested YAML for the same setting are read the same way, and in Compose files it reads settings passed as environment variables (xpack.security.enabled=false, ES_SETTING_..., ELASTICSEARCH_PASSWORD) and the ports each service publishes. It works out whether a node can be reached from the network (network.host, http.host, transport.host, server.host, published ports) and judges the security rules from that, using the real defaults: Elasticsearch 8.0 and later turn security on and set up TLS on first start, 7.x and older leave security off, and the OpenSearch image installs the demo security setup unless told not to. So Elasticsearch 8's own auto-generated configuration is not flagged, and a local development node gets a review note instead of a block. It never connects to a cluster. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • E01: Elasticsearch security off on a reachable node: xpack.security.enabled: false, or a 7.x or older image that never turns it on, with a network address or a port published on every interface
    • E02: the OpenSearch security plugin disabled (plugins.security.disabled, DISABLE_SECURITY_PLUGIN) on a reachable node
    • E03: passwords, tokens and client secrets written in the files: elasticsearch.password, opensearch.password, serviceAccountToken, bind_password, keystore passwords, ELASTIC_PASSWORD, OPENSEARCH_INITIAL_ADMIN_PASSWORD and passwords inside host URLs
    • E04: the OpenSearch demo security setup (allow_unsafe_democertificates: true, or the Docker image's default demo install) on a reachable node

    REVIEW

    • E11: security turned off on a node that is not reachable yet
    • E12: CORS open to any origin (http.cors.allow-origin: "", Kibana server.cors with its default [""])
    • E13: no HTTPS on a network address (xpack.security.http.ssl, plugins.security.ssl.http, server.ssl for Kibana and Dashboards)
    • E14: certificate checks turned off (verification_mode: none, verificationMode: none)
    • E15: Kibana encryption keys or the Dashboards cookie password written in the file
    • E16: action.destructive_requires_name: false, which turns off Elasticsearch 8's guard against DELETE /*
    • E17: anonymous access (anonymous roles, a Kibana anonymous provider, Dashboards anonymous_auth_enabled)
    • E18: a node on a network address whose file never configures security, so it depends on the version

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example project (a Compose stack with Elasticsearch, Kibana and OpenSearch, a production elasticsearch.yml and kibana.yml, an OpenSearch node with the demo setup, OpenSearch Dashboards, an old 7.x node and a development node), and the real report the scanner produces on the risky one

    Limits It reads each file as written. Values from .env files, the keystores, -E command-line options, Helm charts and Kubernetes manifests (including ECK) are not read, Compose services built from other images (such as Bitnami) are skipped, and the OpenSearch security plugin's own files (internal_users.yml, roles.yml), users and roles inside the cluster, firewalls and hosted services are not checked. NOT FLAGGED is not a guarantee.

    Static check of Elasticsearch, Kibana, OpenSearch and OpenSearch Dashboards settings files and Compose services that run the official images. The version of a settings file is not known, keystores and .env files are not read, and the running cluster is not checked. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert passwords and keys (NOTREAL-...) for the scanner to find. No cluster is started or contacted.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads elasticsearch.yml, kibana.yml, OpenSearch files and Compose files as text. It never calls a node or Kibana.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example Elasticsearch and OpenSearch setup, and the real report the scanner prints on the risky example.

    New in Data & Databases