{
  "id": "db-defaults",
  "title": "Configure database defaults",
  "url": "https://redis.io/docs/latest/operate/rs/7.8/databases/configure/db-defaults/",
  "summary": "Cluster-wide policies that determine default settings when creating new databases.",
  "content": "\nDatabase defaults are cluster-wide policies that determine default settings when creating new databases.\n\n## Edit database defaults\n\nTo edit default database configuration using the Cluster Manager UI:\n\n1. On the **Databases** screen, select  to open a list of additional actions.\n\n1. Select **Database defaults**.\n\n1. Configure [database defaults](#db-defaults).\n\n    \n\n1. Select **Save**.\n\n## Database defaults {#db-defaults}\n\n### Endpoint configuration\n\nYou can choose a predefined endpoint configuration to use the recommended database proxy and shards placement policies for your use case. If you want to set these policies manually instead, select **Custom** endpoint configuration.\n\n| Endpoint configuration | Database proxy | Shards placement | Description |\n|-----------|------------|----------------|------------------|------------|\n| Enterprise clustering | Single | Dense | Sets up a single endpoint that uses DNS to automatically reflect IP address updates after failover or topology changes. |\n| Using a load balancer | All nodes | Sparse | Configure Redis with a load balancer like HAProxy or Nginx for environments without DNS. |\n| Multiple endpoints | All primary shards | Sparse | To set up multiple endpoints, enable **OSS Cluster API** in the database settings and ensure client support. Clients initially connect to the primary node to retrieve the cluster topology, which allows direct connections to individual Redis proxies on each node. |\n| Custom | Single, all primary shards, or all nodes | Dense or sparse | Manually choose default database proxy and shards placement policies. |\n\n### Database proxy\n\nRedis Enterprise Software uses [proxies]() to manage and optimize access to database shards. Each node in the cluster runs a single proxy process, which can be active (receives incoming traffic) or passive (waits for failovers).\n\nYou can configure default [proxy policies]() to determine which nodes' proxies are active and bound to new databases by default.\n\nTo configure the default database proxy policy using the Cluster Manager UI:\n\n1. [**Edit database defaults**](#edit-database-defaults). \n\n1. Select a predefined [**Endpoint Configuration**](#endpoint-configuration) to use a recommended database proxy policy, or choose **Custom** to set the policy manually. Changing the database proxy default in the Cluster Manager UI affects both sharded and non-sharded proxy policies.\n\n    \n\n#### Non-sharded proxy policy\n\nTo configure the default proxy policy for non-sharded databases, use one of the following methods:\n\n- [rladmin tune cluster](): \n    \n    ```sh\n    rladmin tune cluster default_non_sharded_proxy_policy { single | all-master-shards | all-nodes }\n    ```\n\n- [Update cluster policy]() REST API request:\n\n    ```sh\n    PUT /v1/cluster/policy \n    { \"default_non_sharded_proxy_policy\": \"single | all-master-shards | all-nodes\" }\n    ```\n\n#### Sharded proxy policy\n\nTo configure the default proxy policy for sharded databases, use one of the following methods:\n\n- [rladmin tune cluster](): \n    \n    ```sh\n    rladmin tune cluster default_sharded_proxy_policy { single | all-master-shards | all-nodes }\n    ```\n\n- [Update cluster policy]() REST API request:\n\n    ```sh\n    PUT /v1/cluster/policy \n    { \"default_sharded_proxy_policy\": \"single | all-master-shards | all-nodes\" }\n    ```\n\n### Shards placement\n\nThe default [shard placement policy]() determines the distribution of database shards across nodes in the cluster.\n\nShard placement policies include:\n\n- `dense`: places shards on the smallest number of nodes.\n\n- `sparse`: spreads shards across many nodes.\n\nTo configure default shard placement, use one of the following methods:\n\n- Cluster Manager UI:\n\n    1. [**Edit database defaults**](#edit-database-defaults). \n\n    1. Select a predefined [**Endpoint Configuration**](#endpoint-configuration) to use a recommended shards placement policy, or choose **Custom** to set the policy manually.\n\n        \n\n- [rladmin tune cluster](): \n    \n    ```sh\n    rladmin tune cluster default_shards_placement { dense | sparse }\n    ```\n\n- [Update cluster policy]() REST API request:\n\n    ```sh\n    PUT /v1/cluster/policy \n    { \"default_shards_placement\": \"dense | sparse\" }\n    ```\n\n### Database version\n\nNew databases use the default Redis database version unless you select a different **Database version** when you [create a database]() in the Cluster Manager UI or specify the `redis_version` in a [create database REST API request]().\n\nTo configure the Redis database version, use one of the following methods:\n\n- Cluster Manager UI: Edit **Database version** in [**Database defaults**](#edit-database-defaults)\n\n\n- [rladmin tune cluster](): \n    \n    ```sh\n    rladmin tune cluster default_redis_version \u003cx.y\u003e\n    ```\n\n- [Update cluster policy]() REST API request:\n\n    ```sh\n    PUT /v1/cluster/policy \n    { \"default_provisioned_redis_version\": \"x.y\" }\n    ```\n\n### Internode encryption\n\nEnable [internode encryption]() to encrypt data in transit between nodes for new databases by default.\n\nTo enable or turn off internode encryption by default, use one of the following methods:\n\n- Cluster Manager UI: Edit **Internode Encryption** in [**Database defaults**](#edit-database-defaults)\n\n- [rladmin tune cluster](): \n    \n    ```sh\n    rladmin tune cluster data_internode_encryption { enabled | disabled }\n    ```\n\n- [Update cluster policy]() REST API request:\n\n    ```sh\n    PUT /v1/cluster/policy \n    { \"data_internode_encryption\": \u003cboolean\u003e }\n    ```\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-04-01T08:10:08-05:00"
}