- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Setting Up X-Pack
- Breaking Changes
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing the Elastic Stack
- Getting Started with Security
- How Security Works
- Setting Up User Authentication
- Configuring SAML Single-Sign-On on the Elastic Stack
- Configuring Role-based Access Control
- Auditing Security Events
- Encrypting Communications
- Restricting Connections with IP Filtering
- Cross Cluster Search, Tribe, Clients and Integrations
- Reference
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Getting Help
- X-Pack security
- Can’t log in after upgrading to 6.2.4
- Some settings are not returned via the nodes settings API
- Authorization exceptions
- Users command fails due to extra arguments
- Users are frequently locked out of Active Directory
- Certificate verification fails for curl on Mac
- SSLHandshakeException causes connections to fail
- Common SSL/TLS exceptions
- Internal Server Error in Kibana
- Setup-passwords command fails due to connection failure
- X-Pack Watcher
- X-Pack monitoring
- X-Pack machine learning
- Limitations
- License Management
- Release Notes
WARNING: Version 6.2 of the Elastic Stack 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.
Encrypting Sensitive Data in Watcher
editEncrypting Sensitive Data in Watcher
editWatches might have access to sensitive data such as HTTP basic authentication information or details about your SMTP email service. You can encrypt this data by generating a key and adding some secure settings on each node in your cluster.
To encrypt sensitive data in Watcher:
- Use the syskeygen command to create a system key file.
-
Copy the
system_key
file to all of the nodes in your cluster.The system key is a symmetric key, so the same key must be used on every node in the cluster.
-
Set the
xpack.watcher.encrypt_sensitive_data
setting:xpack.watcher.encrypt_sensitive_data: true
-
Set the
xpack.watcher.encryption_key
setting in the Elasticsearch keystore on each node in the cluster.For example, run the following command to import the
system_key
file on each node:bin/elasticsearch-keystore add-file xpack.watcher.encryption_key <filepath>/system_key
-
Delete the
system_key
file on each node in the cluster.
Existing watches are not affected by these changes. Only watches that you create after following these steps have encryption enabled.