This functionality is in beta and is subject to change. The design and code is considered to be less mature than official GA features. Elastic will take a best effort approach to fix any issues, but beta features are not subject to the support SLA of official GA features.
« Grant users access to Heartbeat indices Set the password for the beats_system built-in user »
Elastic Docs ›Heartbeat Reference [6.3] ›Securing Heartbeat ›Configure Heartbeat to use X-Pack security

Configure Heartbeat to use encrypted connections

edit

Configure 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.
« Grant users access to Heartbeat indices Set the password for the beats_system built-in user »