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/opendistro_security
folder on all nodes, and delete the opendistro_security
configuration entries from elasticsearch.yml
.
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. To learn more, see Standalone Kibana plugin install.
RPM
- Remove all
opendistro_security
lines fromkibana.yml
. - Change
elasticsearch.url
inkibana.yml
tohttp://
rather thanhttps://
. sudo /usr/share/kibana/bin/kibana-plugin remove opendistro_security
.sudo systemctl restart kibana.service
Docker
-
Create a new
Dockerfile
:FROM amazon/opendistro-for-elasticsearch-kibana:0.9.0 RUN /usr/share/kibana/bin/kibana-plugin remove opendistro_security
-
To build the new Docker image, run:
docker build --tag=kibana-no-security .
- In
docker-compose.yml
, changeamazon/opendistro-for-elasticsearch-kibana:0.9.0
tokibana-no-security
. - Change
ELASTICSEARCH_URL
(docker-compose.yml
) orelasticsearch.url
(your customkibana.yml
) tohttp://
rather thanhttps://
. - Change
ELASTICSEARCH_HOSTS
orelasticsearch.hosts
tohttp://
rather thanhttps://
. - Remove all
opendistro_security
lines fromkibana.yml
. docker-compose up
.