{
  "id": "internode-encryption",
  "title": "Internode encryption",
  "url": "https://redis.io/docs/latest/operate/rs/7.8/security/encryption/internode-encryption/",
  "summary": "Describes internode encryption which improves the security of data in transit.",
  "content": "As of v6.2.4, Redis Enterprise Software supports _internode encryption_, which encrypts internal communication between nodes. This improves the security of data as it travels within a cluster.\n\nInternode encryption is enabled for the _control plane_, which manages the cluster and its databases.\n\nInternode encryption is supported for the _data plane_, which encrypts communication used to replicate shards between nodes and proxy communication with shards located on different nodes.\n\nThe following diagram shows how this works.\n\n\n\nData internode encryption is disabled by default for individual databases in order to optimize for performance.  Encryption adds latency and overhead; the impact is measurable and varies according to the database, its field types, and the details of the underlying use case. \n\nYou can enable data internode encryption for a database by changing the database configuration settings.  This lets you choose when to favor performance and when to encrypt data.\n\n## Prerequisites\n\nInternode encryption requires certain prerequisites.  \n\nYou need to:\n\n- Upgrade all nodes in the cluster to v6.2.4 or later.\n\n- Open port 3342 for the TLS channel used for encrypted communication.\n\n\n## Enable data internode encryption\n\nTo enable internode encryption for a database (also called _data internode encryption_), you need to enable the appropriate setting for each database you wish to encrypt.  To do so, you can:\n\n- Use the Cluster Manager UI to enable the **Internode Encryption** setting from the database **Security** screen.\n\n-  Use the `rladmin` command-line utility to set the [data_internode_encryption]() setting for the database:\n\n    ``` shell\n    rladmin tune db \u003cdatabase_id\u003e data_internode_encryption enabled\n    ``` \n\n- Use the Redis Enterprise Software REST API to set the `data_internode_encryption` setting for the database.\n\n    ``` rest\n    put /v1/bdbs/${database_id}\n    { \"data_internode_encryption\" : true }\n    ```\n\nWhen you change the data internode encryption setting for a database, all active remote client connections are disconnected.  This restarts the internal (DMC) proxy and disconnects all client connections.\n\n## Change cluster policy\n\nTo enable internode encryption for new databases by default, use one of the following methods:\n\n- Cluster Manager UI\n\n    1. On the **Databases** screen, select  to open a list of additional actions.\n\n    1. Select **Database defaults**.\n\n    1. Go to **Internode Encryption** and click **Change**.\n\n    1. Select **Enabled** to enable internode encryption for new databases by default.\n\n    1. Click **Change**.\n\n    1. Select **Save**.\n\n- [rladmin tune cluster](): \n    \n    ```sh\n    rladmin tune cluster data_internode_encryption enabled\n    ```\n\n- [Update cluster policy]() REST API request:\n\n    ```sh\n    PUT /v1/cluster/policy \n    { \"data_internode_encryption\": true }\n    ```\n\n## Encryption ciphers and settings\n\nTo encrypt internode communications, Redis Enterprise Software uses TLS 1.2 and the following cipher suites:\n\n- ECDHE-RSA-AES256-GCM-SHA384\n- ECDHE-RSA-AES128-GCM-SHA256\n\nAs of Redis Enterprise Software v7.4, internode encryption also supports TLS 1.3 with the following cipher suites:\n\n- TLS_AES_128_GCM_SHA256\n- TLS_AES_256_GCM_SHA384\n\nThe TLS layer determines which TLS version to use.\n\nNo configurable settings are exposed; internode encryption is used internally within a cluster and not exposed to any outside service.\n\n## Certificate authority and rotation\n\nStarting with v6.2.4, internode communication is managed, in part, by two certificates: one for the control plane and one for the data plane.  These certificates are signed by a private certificate authority (CA).  The CA is not exposed outside of the cluster, so it cannot be accessed by external processes or services.  In addition, each cluster generates a unique CA that is not used anywhere else.\n\nThe private CA is generated when a cluster is created or upgraded to 6.2.4.  \n\nWhen nodes join the cluster, the cluster CA is used to generate certificates for the new node, one for each plane.  Certificates signed by the private CA are not shared between clusters and they're not exposed outside the cluster.\n\nAll certificates signed by the internal CA expire after ninety (90) days and automatically rotate every thirty (30) days.  Alerts also monitor certificate expiration and trigger when certificate expiration falls below 45 days.  If you receive such an alert, contact support.\n\nYou can use the Redis Enterprise Software REST API to rotate certificates manually:\n\n``` rest\nPOST /v1/cluster/certificates/rotate\n```\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-04-01T08:10:08-05:00"
}