Remote clusters strong identity verification configuration on ECH #4895
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Vale Linting ResultsSummary: 2 suggestions found 💡 Suggestions (2)
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Contributor
🔍 Preview links for changed docs |
eedugon
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This PR adds the instructions to configure strong identity verification on ECH.
To accomplish this:
I've moved the feature description that was documented in self-managed docs to the generic
security-models.mddoc and converted to a snippet.Now the feature is presented for
stack: 9.3.We have created a new doc for this configuration, following a similar structure and pattern than the self-managed document. This new doc (similarly to the self-managed doc) provides the specific steps for strong identity verification, which need to be followed in addition to the remote cluster feature configuration with API keys authentication.
In the ECH docs about remote clusters we are linking to this procedure for strong identity verification configuration.
Closes https://github.com/elastic/docs-content-internal/issues/610
Generative AI disclosure
Tool(s) and model(s) used: Cursor in Auto mode.