Open Distro development has moved to OpenSearch. The Open Distro plugins will continue to work with legacy versions of Elasticsearch OSS, but we recommend upgrading to OpenSearch to take advantage of the latest features and improvements.
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
A more permanent option is to remove the security plugin entirely. Delete the
plugins/opendistro_security folder on all nodes, and delete the
opendistro_security configuration entries from
To perform these steps on the Docker image, see Customize the Docker image.
Disabling or removing the plugin exposes the configuration index for the security plugin. 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. For more information, see Standalone Kibana plugin install.
RPM or DEB
- Remove all
sudo /usr/share/kibana/bin/kibana-plugin remove opendistroSecurityKibana.
sudo systemctl restart kibana.service.
Create a new
FROM amazon/opendistro-for-elasticsearch-kibana:1.13.3 RUN /usr/share/kibana/bin/kibana-plugin remove opendistroSecurityKibana COPY --chown=kibana:kibana kibana.yml /usr/share/kibana/config/
In this case,
kibana.ymlis a “vanilla” version of the file with no Open Distro entries. It might look like this:
--- server.name: kibana server.host: "0" elasticsearch.hosts: http://localhost:9200
To build the new Docker image, run the following command:
docker build --tag=kibana-no-security .