Disable security

You might want to temporarily disable the Security plugin to make testing or internal usage more straightforward. To disable the plugin, add the following line in elasticsearch.yml:

opendistro_security.disabled: true

A more permanent option is to remove the Security plugin entirely. Delete the plugins/security folder on all nodes, and delete the opendistro_security configuration entries from elasticsearch.yml.

Disabling or removing the plugin exposes the security configuration index. If the index contains sensitive information, be sure to protect it through some other means. If you no longer need the index, delete it.

Remove Kibana plugin

The Security plugin is actually two plugins: one for Elasticsearch and one for Kibana. You can use the Elasticsearch plugin independently, but the Kibana plugin depends on a secured Elasticsearch cluster.

If you disable the Security plugin in elasticsearch.yml (or delete the plugin entirely) and still want to use Kibana, you must remove the corresponding Kibana plugin.

After the removal of any plugin, Kibana performs an “optimize” operation the next time you start it. This operation takes several minutes even on fast machines, so be patient.


  1. Remove all opendistro_security lines from kibana.yml.
  2. Change elasticsearch.url in kibana.yml to http:// rather than https://.
  3. sudo /usr/share/kibana/bin/kibana-plugin remove opendistro_security.
  4. sudo systemctl restart kibana.service


  1. Create a new Dockerfile:

    FROM amazon/opendistro-for-elasticsearch-kibana:0.8.0
    RUN /usr/share/kibana/bin/kibana-plugin remove opendistro_security
  2. To build the new Docker image, run:

    docker build --tag=kibana-no-security .
  3. In docker-compose.yml, change amazon/opendistro-for-elasticsearch-kibana:0.8.0 to kibana-no-security.
  4. Change ELASTICSEARCH_URL (docker-compose.yml) or elasticsearch.url (your custom kibana.yml) to http:// rather than https://.
  5. Remove all opendistro_security lines from kibana.yml.
  6. docker-compose up.