From 6f9f38654ca4730112cf40ff430095dc292b241b Mon Sep 17 00:00:00 2001 From: Karen Metts Date: Fri, 24 Oct 2025 16:44:18 -0400 Subject: [PATCH] Doc: Update Logstash security settings --- docs/reference/ls-to-ls-http.md | 12 ++++++------ docs/reference/secure-connection.md | 2 +- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/reference/ls-to-ls-http.md b/docs/reference/ls-to-ls-http.md index ceb9ae59dc5..128afa15bd7 100644 --- a/docs/reference/ls-to-ls-http.md +++ b/docs/reference/ls-to-ls-http.md @@ -96,9 +96,9 @@ It is important that you secure the communication between Logstash instances. Us 3. Configure the upstream (sending) Logstash to use SSL. Add these settings to the HTTP output configuration: - * `cacert`: Configures the Logstash client to trust any certificates signed by the specified CA. - * `client_key`: Specifies the key the Logstash client uses to authenticate with the Logstash server. - * `client_cert`: Specifies the certificate that the Logstash client uses to authenticate to the Logstash server. + * `ssl_certificate_authorities`: Configures the Logstash client to trust any certificates signed by the specified CA. + * `ssl_key`: Specifies the key the Logstash client uses to authenticate with the Logstash server. + * `ssl_certification`: Specifies the certificate that the Logstash client uses to authenticate to the Logstash server. For example: @@ -107,9 +107,9 @@ It is important that you secure the communication between Logstash instances. Us http { ... - cacert => "ca.crt" - client_key => "client.key.pk8" - client_cert => "client.crt" + ssl_certificate_authorities => "ca.crt" + ssl_key => "client.key.pk8" + ssl_certificate => "client.crt" } } ``` diff --git a/docs/reference/secure-connection.md b/docs/reference/secure-connection.md index 775ea5821df..6f8b3edda3e 100644 --- a/docs/reference/secure-connection.md +++ b/docs/reference/secure-connection.md @@ -289,7 +289,7 @@ Tips for creating API keys: * API keys are tied to the cluster they are created in. If you are sending output to different clusters, be sure to create the correct kind of API key. * {{ls}} can send both collected data and monitoring information to {{es}}. If you are sending both to the same cluster, you can use the same API key. For different clusters, you need an API key per cluster. -* A single cluster can share a key for ingestion and monitoring purposes. +* A single cluster can share a key for ingestion and monitoring. * A production cluster and a monitoring cluster require separate keys. * When you create an API key for {{ls}}, select **Logstash** from the **API key format** dropdown. This option formats the API key in the correct `id:api_key` format required by {{ls}}.