- Heartbeat Reference: other versions:
- Overview
- Get started
- Set up and run
- Configure
- Monitors
- General settings
- Project paths
- Output
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Processors
- Define processors
- add_cloud_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_json_fields
- decompress_gzip_field
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- registered_domain
- rename
- truncate_fields
- Autodiscover
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- heartbeat.reference.yml
- How to guides
- Exported fields
- Beat fields
- Cloud provider metadata fields
- Common heartbeat monitor fields
- Docker fields
- ECS fields
- Host fields
- HTTP monitor fields
- ICMP fields
- Jolokia Discovery autodiscover provider fields
- Kubernetes fields
- Process fields
- Host lookup fields
- SOCKS5 proxy fields
- Monitor summary fields
- TCP layer fields
- TLS encryption layer fields
- Monitor
- Secure
- Troubleshoot
- Contribute to Beats
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Configure Heartbeat to use security features
editConfigure Heartbeat to use security features
editIf you want Heartbeat to connect to a cluster that has security features enabled, there are extra configuration steps:
-
Grant users access to secured resources.
You can use role-based access control to grant Heartbeat users access to secured resources.
-
You can use API keys to grant access to Elasticsearch more securely.
-
Configure authentication credentials.
To interact with a secured cluster, Heartbeat must either provide basic authentication credentials or present a client certificate.
-
Configure Heartbeat to use encrypted connections.
If encryption is enabled on the cluster, you need to enable HTTPS in the Heartbeat configuration.
For more information about security features, see Secure a cluster.
Was this helpful?
Thank you for your feedback.