From bd6653fbee8349da8ef87ec3ff5e7b3b668ede6a Mon Sep 17 00:00:00 2001 From: Albert Zaharovits Date: Sun, 1 Jul 2018 11:11:47 +0300 Subject: [PATCH] [DOCS] Secure settings specified per node (#31621) Make it clear that secure settings have to be set on each cluster node. --- docs/reference/setup/secure-settings.asciidoc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/reference/setup/secure-settings.asciidoc b/docs/reference/setup/secure-settings.asciidoc index 78731f7663d11..1474ba137697d 100644 --- a/docs/reference/setup/secure-settings.asciidoc +++ b/docs/reference/setup/secure-settings.asciidoc @@ -1,5 +1,5 @@ [[secure-settings]] -=== Secure Settings +=== Secure settings Some settings are sensitive, and relying on filesystem permissions to protect their values is not sufficient. For this use case, Elasticsearch provides a @@ -16,6 +16,10 @@ Elasticsearch. NOTE: The elasticsearch keystore currently only provides obfuscation. In the future, password protection will be added. +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. + [float] [[creating-keystore]] === Creating the keystore