[9.0] (backport #17688) Doc: Add clarification about API key format for Logstash #17748
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
* Add clarification about API key format for Logstash (cherry picked from commit b238824)
vishaangelova
approved these changes
Jun 27, 2025
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.
Release notes
[rn:skip]
What does this PR do?
This PR clarifies the API key format required for Logstash in the following docs:
docs/reference/secure-connection.mddocs/reference/connecting-to-cloud.mddocs/reference/using-logstash-with-elastic-integrations.mdRelated issues
Closes #17687
Changes
(All links are to the PR preview)
Added clarification in the Security to Elastic Cloud Serverless and Security to hosted Elasticsearch Service admonitions under Elasticsearch security on by default(UPDATE: Removed after the review round)and Extend Integrations with Logstashto make them more explicit with respect to the API key format and how it is constructedPreviews
https://docs-v3-preview.elastic.dev/elastic/logstash/pull/17688/reference
https://docs-v3-preview.elastic.dev/elastic/logstash/pull/17688/reference/secure-connection
https://docs-v3-preview.elastic.dev/elastic/logstash/pull/17688/reference/connecting-to-cloud
https://docs-v3-preview.elastic.dev/elastic/logstash/pull/17688/reference/using-logstash-with-elastic-integrations(UPDATE: After the review round, I’ve decided to keep this file unchanged.)This is an automatic backport of pull request #17688 done by Mergify.