Skip to content

Add note about extended key usage for Logstash output #1758

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add note about extended key usage for Logstash output #1758

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/en/ingest-management/security/logstash-certificates.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,15 @@ cluster. For more information, refer to the
You can use whatever process you typically use to generate PEM-formatted
certificates. The examples shown here use the `certutil` tool provided by {es}.

TIP: The `certutil` tool is not available on {ecloud}, but you can still use it
[TIP]
====
* The `certutil` tool is not available on {ecloud}, but you can still use it
to generate certificates for {agent} to {ls} connections. Just
https://www.elastic.co/downloads/elasticsearch[download an {es} package],
extract it to a local directory, and run the `elasticsearch-certutil` command.
There's no need to start {es}!
* If you choose not to use link:https://www.elastic.co/guide/en/elasticsearch/reference/8.17/certutil.html[certutil], the certificates that you obtain must allow for both clientAuth and serverAuth if the extended key usage extension is present.
====

. Generate a certificate authority (CA). Skip this step if you want to use an
existing CA.
Expand Down
Loading