Skip to content

Commit 4450757

Browse files
committed
Add note about extended key usage for Logstash output
1 parent 42bbc05 commit 4450757

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/en/ingest-management/security/logstash-certificates.asciidoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,11 +28,15 @@ cluster. For more information, refer to the
2828
You can use whatever process you typically use to generate PEM-formatted
2929
certificates. The examples shown here use the `certutil` tool provided by {es}.
3030

31-
TIP: The `certutil` tool is not available on {ecloud}, but you can still use it
31+
[TIP]
32+
====
33+
* The `certutil` tool is not available on {ecloud}, but you can still use it
3234
to generate certificates for {agent} to {ls} connections. Just
3335
https://www.elastic.co/downloads/elasticsearch[download an {es} package],
3436
extract it to a local directory, and run the `elasticsearch-certutil` command.
3537
There's no need to start {es}!
38+
* 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.
39+
====
3640

3741
. Generate a certificate authority (CA). Skip this step if you want to use an
3842
existing CA.

0 commit comments

Comments
 (0)