{
  "id": "license-keys",
  "title": "Cluster license keys",
  "url": "https://redis.io/docs/latest/operate/rs/8.0/clusters/configure/license-keys/",
  "summary": "The cluster key (or license) enables features and capacity within Redis Enterprise Software",
  "content": "The cluster license key enables Redis Software features and determines shard usage and limits.\nYou can add or update a cluster key at any time.\n\nA single license can only be deployed on a single cluster. Each cluster, including passive or cold standby clusters used for disaster recovery, requires its own separate license, regardless of whether all clusters are active simultaneously.\n\n## Trial mode\n\nTrial mode allows all features to be enabled during the trial period.\n\nTrial mode is limited to 30 days and 4 shards, including master and replica shards. A new Redis Software installation starts its 30-day trial period from the day you set up the cluster on the first node.\n\nTrial mode requires a trial license. If you do not provide a license when you create a cluster using the Cluster Manager UI or a [bootstrapping REST API request](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/bootstrap#post-bootstrap), a trial cluster license is generated by default.\n\n## View cluster license key\n\nTo view the cluster license key, use a [`GET /v1/license`](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/license#get-license) REST API request. For a list of returned fields, see the [response section](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/license#get-response).\n\n\nAs of version 7.2, Redis Software enforces shard limits by shard types, RAM or flash, instead of the total number of shards. The flash shards limit only appears in the UI if Auto Tiering is enabled.\n\n\n## Update cluster license\n\n\nAfter you add a cluster key, you cannot remove the key to return the cluster to trial mode.\n\n\nYou can update the cluster license key:\n\n- During cluster setup using the Cluster Manager UI or CLI\n\n- After cluster setup using the Cluster Manager UI:\n\n    1. Go to **Cluster \u003e Configuration \u003e General \u003e License**.\n    \n    1. Select **Change**.\n\n    1. Upload or enter your cluster license key.\n    \n    1. Select **Save**.\n\nYou can update an existing cluster key at any time.\nRedis Software checks its validity for the following:\n- Cluster name\n- Activation and expiration dates\n- Shard usage and limits\n- Features\n\nIf saving a new cluster key fails, the operation returns an error with the failure's cause.\nIn this case, the existing key stays in effect.\n\n## Expired cluster license\n\nWhen the license is expired:\n\n- You cannot do these actions:\n\n    - Change database settings, including security and configuration options.\n\n    - Add a database.\n\n- You can do these actions:\n\n    - Sign in to the Cluster Manager UI and view settings and metrics at all resolutions for the cluster, nodes, and databases.\n\n    - Change cluster settings, including the license key, security for administrators, and cluster alerts.\n\n    - Fail over when a node fails and explicitly migrate shards between nodes.\n\n    - Upgrade a node to a new version of Redis Software.\n\n## Configure license expiration alert\n\nBy default, a cluster license alert is scheduled to occur 7 days before the cluster license expiration date.\n\n![images/rs/screenshots/cluster/cluster-license-expiration-alert.png](https://redis.io/docs/latest/images/rs/screenshots/cluster/cluster-license-expiration-alert.png)\n\nYou can adjust the threshold value of the cluster license expiration alert based on how far in advance you want to be notified of the license expiration. The value should be within a reasonable range that allows your organization enough time to take action, such as renewing the license, before it expires.\n\nTo change the cluster license alert settings, use one of the following methods:\n\n- Cluster Manager UI:\n\n    1. On the **Cluster \u003e Configuration** screen, select the **Alerts Settings** tab.\n\n    1. Click **Edit**.\n\n    1. In the **Cluster utilization** section, enable the alert setting \"License expiry notifications will be sent \\\u003cvalue\\\u003e days before the license expires\" and enter a new value in the box.\n\n        ![images/rs/screenshots/cluster/cluster-config-alert-settings-utilization.png](https://redis.io/docs/latest/images/rs/screenshots/cluster/cluster-config-alert-settings-utilization.png)\n\n    1. Click **Save**.\n\n\n- [Update cluster](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/cluster#put-cluster) REST API request:\n\n    The following example changes the cluster license alert to occur 30 days before the cluster license expiration date:\n\n    ```sh\n    PUT /v1/cluster\n    {\n        \"alert_settings\": {\n            \"cluster_license_about_to_expire\": {\n                \"enabled\": true,\n                \"threshold\": \"30\"\n            }\n        }\n    }\n    ```\n\n## Monitor cluster license\n\nAs of version 7.2, Redis Software exposes the license quotas and the shards consumption metrics in the Cluster Manager UI or via the [Prometheus integration](https://redis.io/docs/latest/integrate/prometheus-with-redis-enterprise/).\n\nThe `cluster_shards_limit` metric displays the total shard limit by shard type.\n\nExamples:\n- `cluster_shards_limit{cluster=\"mycluster.local\",shard_type=\"ram\"} 100.0`\n- `cluster_shards_limit{cluster=\"mycluster.local\",shard_type=\"flash\"} 50.0`\n\nThe `bdb_shards_used` metric displays the used shard count by database and shard type.\n\nExamples:\n- `bdb_shards_used{bdb=\"2\",cluster=\"mycluster.local\",shard_type=\"ram\"} 86.0`\n- `bdb_shards_used{bdb=\"3\",cluster=\"mycluster.local\",shard_type=\"flash\"} 23.0`\n\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-07-23T12:00:25-05:00"
}