Skip to content

Doc: Update Logstash security settings (WIP) #18356

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −7
Draft

Doc: Update Logstash security settings (WIP) #18356

Show file tree
Hide file tree
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
12 changes: 6 additions & 6 deletions docs/reference/ls-to-ls-http.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand All @@ -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"
}
}
```
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/secure-connection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}}.
Expand Down
Loading