New

The executive guide to generative AI

Read more
About usPartnersSupport|Login

WARNING: Version 6.0 of Heartbeat has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Granting Users Access to Heartbeat Indices Troubleshooting »
Elastic Docs ›Heartbeat Reference [6.0] ›Securing Heartbeat ›Heartbeat and X-Pack Security

Configuring Heartbeat to use Encrypted Connections

edit

Configuring Heartbeat 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 Heartbeat configuration.

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

output.elasticsearch:
    hosts: ["https://localhost:9200"] 
    index: "heartbeat"
    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.
« Granting Users Access to Heartbeat Indices Troubleshooting »
Was this helpful?
Feedback