This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
« Grant users access to Functionbeat indices Set the password for the built-in monitoring user »
Elastic Docs ›Functionbeat Reference [6.6] ›Securing Functionbeat ›Configure Functionbeat to use X-Pack security

Configure Functionbeat to use encrypted connections

edit

Configure Functionbeat 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 Functionbeat configuration.

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

output.elasticsearch:
  hosts: ["https://localhost:9200"] 
  index: "functionbeat"
  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 Functionbeat indices Set the password for the built-in monitoring user »