- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Installing X-Pack
- Migrating to X-Pack
- Breaking Changes
- Breaking Changes in 5.5.2
- Breaking Changes in 5.5.0
- Breaking Changes in 5.3
- Breaking Changes in 5.2
- Breaking Changes in 5.0
- Breaking Changes in Shield 2.4.2
- Breaking Changes in Reporting 2.4.1
- Breaking Changes in Shield 2.4.0
- Breaking Changes in Shield 2.1.0
- Breaking Changes in Shield 2.0.1
- Breaking Changes in 2.0.0
- Breaking Changes in Shield 1.3.0
- X-Pack Settings
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing Elasticsearch and Kibana
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Limitations
- License Management
- Release Notes
WARNING: Version 5.6 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 Communications
editEncrypting Communications
editElasticsearch nodes store data that may be confidential. Attacks on the data may come from the network. These attacks could include sniffing of the data, manipulation of the data, and attempts to gain access to the server and thus the files storing the data. Securing your nodes with the procedures below helps to reduce risk from network-based attacks.
This section shows how to:
- Encrypt traffic to, from and within an Elasticsearch cluster using SSL/TLS,
- Require nodes to authenticate as they join the cluster using SSL certificates, and
- Make it more difficult for remote attackers to issue any commands to Elasticsearch.
The authentication of new nodes helps prevent a rogue node from joining the cluster and receiving data through replication.