2017-01-30 17:56:45 -05:00
|
|
|
[[secure-settings]]
|
2018-07-01 04:11:47 -04:00
|
|
|
=== Secure settings
|
2017-01-30 17:56:45 -05:00
|
|
|
|
|
|
|
Some settings are sensitive, and relying on filesystem permissions to protect
|
2017-11-29 03:44:25 -05:00
|
|
|
their values is not sufficient. For this use case, Elasticsearch provides a
|
2018-01-09 18:01:37 -05:00
|
|
|
keystore and the `elasticsearch-keystore` tool to manage the settings in the keystore.
|
2017-01-30 17:56:45 -05:00
|
|
|
|
2017-11-29 03:44:25 -05:00
|
|
|
NOTE: All commands here should be run as the user which will run Elasticsearch.
|
2017-01-30 17:56:45 -05:00
|
|
|
|
2017-06-14 00:04:16 -04:00
|
|
|
NOTE: Only some settings are designed to be read from the keystore. See
|
|
|
|
documentation for each setting to see if it is supported as part of the keystore.
|
|
|
|
|
2017-11-30 17:19:58 -05:00
|
|
|
NOTE: All the modifications to the keystore take affect only after restarting
|
|
|
|
Elasticsearch.
|
|
|
|
|
2018-01-09 18:01:37 -05:00
|
|
|
NOTE: The elasticsearch keystore currently only provides obfuscation. In the future,
|
|
|
|
password protection will be added.
|
|
|
|
|
2018-07-01 04:11:47 -04:00
|
|
|
These settings, just like the regular ones in the `elasticsearch.yml` config file,
|
|
|
|
need to be specified on each node in the cluster. Currently, all secure settings
|
|
|
|
are node-specific settings that must have the same value on every node.
|
|
|
|
|
2017-01-30 17:56:45 -05:00
|
|
|
[float]
|
|
|
|
[[creating-keystore]]
|
|
|
|
=== Creating the keystore
|
|
|
|
|
|
|
|
To create the `elasticsearch.keystore`, use the `create` command:
|
|
|
|
|
|
|
|
[source,sh]
|
|
|
|
----------------------------------------------------------------
|
|
|
|
bin/elasticsearch-keystore create
|
|
|
|
----------------------------------------------------------------
|
|
|
|
|
|
|
|
The file `elasticsearch.keystore` will be created alongside `elasticsearch.yml`.
|
|
|
|
|
|
|
|
[float]
|
|
|
|
[[list-settings]]
|
|
|
|
=== Listing settings in the keystore
|
|
|
|
|
|
|
|
A list of the settings in the keystore is available with the `list` command:
|
|
|
|
|
|
|
|
[source,sh]
|
|
|
|
----------------------------------------------------------------
|
2017-07-21 05:24:27 -04:00
|
|
|
bin/elasticsearch-keystore list
|
2017-01-30 17:56:45 -05:00
|
|
|
----------------------------------------------------------------
|
|
|
|
|
|
|
|
[float]
|
|
|
|
[[add-string-to-keystore]]
|
|
|
|
=== Adding string settings
|
|
|
|
|
|
|
|
Sensitive string settings, like authentication credentials for cloud
|
2017-04-05 05:15:08 -04:00
|
|
|
plugins, can be added using the `add` command:
|
2017-01-30 17:56:45 -05:00
|
|
|
|
|
|
|
[source,sh]
|
|
|
|
----------------------------------------------------------------
|
|
|
|
bin/elasticsearch-keystore add the.setting.name.to.set
|
|
|
|
----------------------------------------------------------------
|
|
|
|
|
|
|
|
The tool will prompt for the value of the setting. To pass the value
|
|
|
|
through stdin, use the `--stdin` flag:
|
|
|
|
|
|
|
|
[source,sh]
|
|
|
|
----------------------------------------------------------------
|
|
|
|
cat /file/containing/setting/value | bin/elasticsearch-keystore add --stdin the.setting.name.to.set
|
|
|
|
----------------------------------------------------------------
|
|
|
|
|
|
|
|
[float]
|
|
|
|
[[remove-settings]]
|
|
|
|
=== Removing settings
|
|
|
|
|
|
|
|
To remove a setting from the keystore, use the `remove` command:
|
|
|
|
|
|
|
|
[source,sh]
|
|
|
|
----------------------------------------------------------------
|
|
|
|
bin/elasticsearch-keystore remove the.setting.name.to.remove
|
|
|
|
----------------------------------------------------------------
|
|
|
|
|