Doc: Add clarification about API key format for Logstash #17688
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
vishaangelova
added
enhancement
docs
backport-active-9
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
vishaangelova
force-pushed
the
serverless-clarify-api-key-when-using-logstash
branch
from
ee532b4 to
aea8d98
Compare
vishaangelova
force-pushed
the
serverless-clarify-api-key-when-using-logstash
branch
from
aea8d98 to
c6d674e
Compare
|
Looking... |
ppf2
reviewed
Jun 5, 2025
docs/reference/index.md
Outdated
| @@ -19,7 +19,7 @@ Logstash accelerates your insights by harnessing a greater volume and variety of | |||
| You’ll use the {{ls}} [{{es}} output plugin](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md) to send data to {{serverless-full}}. | |||
| Note these differences between {{es-serverless}} and both {{ess}} and self-managed {{es}}: | |||
|
|
|||
| * Use **API keys** to access {{serverless-full}} from {{ls}}. Any user-based security settings in your [{{es}} output plugin](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md) configuration are ignored and may cause errors. | |||
| * Use [**API keys**](/reference/secure-connection.md#ls-api-keys) to access {{serverless-full}} from {{ls}}. Any user-based security settings in your [{{es}} output plugin](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md) configuration are ignored and may cause errors. | |||
There was a problem hiding this comment.
We can also be more direct and say that Serverless does not support native user authentication. You must use API keys to access Serverless.
ppf2
reviewed
Jun 5, 2025
ppf2
reviewed
Jun 5, 2025
ppf2
reviewed
Jun 5, 2025
ppf2
reviewed
Jun 5, 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)
Previews
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