This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.

NOTE: This You are looking at documentation for an older release. For the latest information, see the current release documentation.

« Grant users access to Journalbeat indices Set the password for the built-in monitoring user »
Elastic Docs ›Journalbeat Reference [6.8] ›Securing Journalbeat ›Configure Journalbeat to use X-Pack security

Configure Journalbeat to use encrypted connections

edit

Configure Journalbeat to use encrypted connections

edit

If encryption is enabled on the Elasticsearch cluster, you need to connect to Elasticsearch via HTTPS. If the certificate authority (CA) that signed your node certificates is not in the host system’s trusted certificate authorities list, you also need to add the path to the .pem file that contains your CA’s certificate to the Journalbeat configuration.

To configure a Journalbeat to connect to Elasticsearch via HTTPS, add the https protocol to all host URLs:

output.elasticsearch:
  hosts: ["https://localhost:9200"] 
  index: "journalbeat"
  ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

Specify the https protocol to connect the Elasticsearch cluster.

Specify the path to the local .pem file that contains your Certificate Authority’s certificate. This is generally only needed if you use your own CA to sign your node certificates.
« Grant users access to Journalbeat indices Set the password for the built-in monitoring user »