Clarify the section on TLS for "Securing the reporting endpoints" #54741
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #49969.
Since this section is focused on establishing trust for the Kibana server's certificate, I changed the documentation to describe the two most likely scenarios:
The old documentation recommended specifying the Kibana server's end-entity certificate as a trusted cert for Elasticsearch. I changed it to recommend specifying the CA certificate instead, which is what the rest of the Kibana documentation refers to regarding TLS connections and trust. This follows PKI best practices, as CA certificates usually have a much longer lifespan than end-entity certificates.