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 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 is required in order to use a production license that enables X-Pack security and helps reduce the 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.