honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Secure settings specified per node (#31621) 

Make it clear that secure settings have to be set
on each cluster node.
This commit is contained in:
Albert Zaharovits 2018-07-01 11:11:47 +03:00 committed by GitHub
parent c827a4e8e1
commit 85ec497056
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/reference/setup/secure-settings.asciidoc
View File

@ -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