Skip to content

Commit

Permalink
[DOCS] Secure settings specified per node (#31621)
Browse files Browse the repository at this point in the history
Make it clear that secure settings have to be set
on each cluster node.
  • Loading branch information
albertzaharovits committed Jul 1, 2018
1 parent 06d0596 commit bd6653f
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion docs/reference/setup/secure-settings.asciidoc
Original file line number Diff line number Diff line change
@@ -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
Expand All @@ -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
Expand Down

0 comments on commit bd6653f

Please sign in to comment.