-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[7.14] [DOCS] Clarify where to complete security steps #76120
[7.14] [DOCS] Clarify where to complete security steps #76120
Conversation
Pinging @elastic/es-security (Team:Security) |
Pinging @elastic/es-docs (Team:Docs) |
+ | ||
[source,yaml] | ||
---- | ||
xpack.security.http.ssl.enabled: true | ||
xpack.security.http.ssl.keystore.path: http.p12 | ||
xpack.security.http.ssl.keystore.path: config/http.p12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The config/
part is not needed. Configuration files are resolved relative to the config directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ywangd -- I'll remove config/
from the path.
@@ -486,8 +488,8 @@ separate monitoring cluster prevents production cluster outages from impacting | |||
your ability to access your monitoring data. It also prevents monitoring | |||
activities from impacting the performance of your production cluster. | |||
|
|||
. From the directory where you installed Elasticsearch, navigate to the | |||
`/kibana` directory that you created when <<encrypt-http-communication,encrypting HTTP client communications for {es}>>. | |||
. On any single node, navigate to the `/kibana` directory that you created when |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be On the node on which you generated the HTTP certificates
? (or neater wording to that effect)
I don't think we would assume that they copied the kibana
directory to every node (though they might have)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good eye @tvernum 👀
I'll change this to read:
. On the node where you <<encrypt-http-communication,generated certificates for the HTTP layer>>, navigate to the
/kibana
directory.
@elasticmachine run elasticsearch-ci/docs |
* [DOCS] Clarify where to complete security steps * Remove config/ from HTTP keystore path * Clarify the node where generating certs for the HTTP layer
* [DOCS] Clarify where to complete security steps * Remove config/ from HTTP keystore path * Clarify the node where generating certs for the HTTP layer
Updates our documentation for Configuring security to indicate which steps need to be taken on every node, and which steps can be performed once on any single node.
Preview link: https://elasticsearch_76120.docs-preview.app.elstc.co/guide/en/elasticsearch/reference/master/configuring-stack-security.html
Closes #76055