Skip to content

Commit bd6653f

Browse files
[DOCS] Secure settings specified per node (#31621)
Make it clear that secure settings have to be set on each cluster node.
1 parent 06d0596 commit bd6653f

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/reference/setup/secure-settings.asciidoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
[[secure-settings]]
2-
=== Secure Settings
2+
=== Secure settings
33

44
Some settings are sensitive, and relying on filesystem permissions to protect
55
their values is not sufficient. For this use case, Elasticsearch provides a
@@ -16,6 +16,10 @@ Elasticsearch.
1616
NOTE: The elasticsearch keystore currently only provides obfuscation. In the future,
1717
password protection will be added.
1818

19+
These settings, just like the regular ones in the `elasticsearch.yml` config file,
20+
need to be specified on each node in the cluster. Currently, all secure settings
21+
are node-specific settings that must have the same value on every node.
22+
1923
[float]
2024
[[creating-keystore]]
2125
=== Creating the keystore

0 commit comments

Comments
 (0)