Secure Sidecar Communication

[Artsiom]

I found the Secure Sidecar Communication section in the documentation.

*" The Communication between Sidecar and Graylog will be secured if your API uses SSL

To secure the communication between the Collector and Graylog you just need to mark Enable TLS in your Beats Input. Without giving additional Information, Graylog will now create a self-signed certificate for this Input. Now in the Sidecar Beats Output Configuration you just mark Enable TLS Support and Insecure TLS connection . After this is saved, the communication between Beats and Graylog will use TLS."

I found "Enable TLS in your Beats Input.".
But how to do it - "Now in the Sidecar Beats Output Configuration you just mark Enable TLS Support and Insecure TLS connection".

I use Graylog Sidecar.

[jan (Jan Doberstein)]

he @Artsiom

that sentence you refer to is a reference to the “old” sidecar where you did not write the complete beats configuration yourself but with a form where you just select by checkboxes.

We need to adjust this guide.

You would write

ssl_verify_mode = none

or reference your internal CA with

  ssl.certificate_authorities: ["ca.cer"]

[Artsiom]

he @jan

I where should i write this?

I write in Collectors Configuration and mark Enable TLS in your Beats Input. Not work, Logs from the client stop coming.