Update instructions for connecting AutoOps to self-managed cluster #3496
+2
−2
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
We should create the Elasticsearch API key or Role from the source side self-managed cluster. We don't need ECH deployment for setting up AutoOps for the self managed cluster.
insukcho
added
bug
🔍 Preview links for changed docs |
insukcho
changed the title
eedugon
approved these changes
Oct 16, 2025
Contributor
eedugon
left a comment
eedugon
left a comment
There was a problem hiding this comment.
Thanks for this, I hope we don't have similar errors in other autoops docs. If you know about anything else feel free to reach out directly to me.
rhr323
pushed a commit
to rhr323/docs-content
that referenced
this pull request
Oct 27, 2025
…lastic#3496) We should create the Elasticsearch API key or Role from the **source side self-managed cluster**. We don't need ECH deployment for setting up AutoOps for the self managed cluster and it is making a big confusion. Co-authored-by: Edu González de la Herrán <[email protected]>
naemono
pushed a commit
to naemono/docs-content
that referenced
this pull request
Oct 28, 2025
…lastic#3496) We should create the Elasticsearch API key or Role from the **source side self-managed cluster**. We don't need ECH deployment for setting up AutoOps for the self managed cluster and it is making a big confusion. Co-authored-by: Edu González de la Herrán <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We should create the Elasticsearch API key or Role from the source side self-managed cluster. We don't need ECH deployment for setting up AutoOps for the self managed cluster and it is making a big confusion.