{
  "schema_version": 2,
  "id": "operate/rs/databases/configure/db-defaults",
  "title": "Configure database defaults",
  "url": "https://redis.io/docs/latest/operate/rs/databases/configure/db-defaults/",
  "summary": "Cluster-wide policies that determine default settings when creating new databases.",
  "tags": [
    "docs",
    "operate",
    "rs"
  ],
  "last_updated": "2026-10-02T16:06:07+01:00",
  "page_type": "content",
  "content_hash": "21606ac0ac1d73f27ea23c937f6d7781d02c19df11e0b3ff5e53dbadd22e3b7c",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "Database defaults are cluster-wide policies that determine default settings when creating new databases."
    },
    {
      "id": "edit-database-defaults",
      "title": "Edit database defaults",
      "role": "content",
      "text": "To edit default database configuration using the Cluster Manager UI:\n\n1. On the **Databases** screen, select ![Toggle actions button](https://redis.io/docs/latest/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.\n\n1. Select **Database defaults**.\n\n1. Configure [database defaults](#db-defaults).\n\n    ![Database defaults configuration panel.](https://redis.io/docs/latest/images/rs/screenshots/databases/db-defaults.png)\n\n1. Select **Save**."
    },
    {
      "id": "db-defaults",
      "title": "Database defaults",
      "role": "content",
      "text": ""
    },
    {
      "id": "endpoint-configuration",
      "title": "Endpoint configuration",
      "role": "content",
      "text": "You 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. |"
    },
    {
      "id": "database-proxy",
      "title": "Database proxy",
      "role": "content",
      "text": "Redis Software uses [proxies](https://redis.io/docs/latest/operate/rs/references/terminology#proxy) 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](https://redis.io/docs/latest/operate/rs/databases/configure/proxy-policy) 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    ![The Database defaults panel lets you select Database proxy and Shards placement if Endpoint Configuration is set to Custom.](https://redis.io/docs/latest/images/rs/screenshots/databases/db-defaults-endpoint-config-custom.png)\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](https://redis.io/docs/latest/operate/rs/references/cli-utilities/rladmin/tune#tune-cluster): \n    \n    [code example]\n\n- [Update cluster policy](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/cluster/policy#put-cluster-policy) REST API request:\n\n    [code example]\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](https://redis.io/docs/latest/operate/rs/references/cli-utilities/rladmin/tune#tune-cluster): \n    \n    [code example]\n\n- [Update cluster policy](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/cluster/policy#put-cluster-policy) REST API request:\n\n    [code example]"
    },
    {
      "id": "shards-placement",
      "title": "Shards placement",
      "role": "content",
      "text": "The default [shard placement policy](https://redis.io/docs/latest/operate/rs/databases/memory-performance/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        ![The Database defaults panel lets you select Database proxy and Shards placement if Endpoint Configuration is set to Custom.](https://redis.io/docs/latest/images/rs/screenshots/databases/db-defaults-endpoint-config-custom.png)\n\n- [rladmin tune cluster](https://redis.io/docs/latest/operate/rs/references/cli-utilities/rladmin/tune#tune-cluster): \n    \n    [code example]\n\n- [Update cluster policy](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/cluster/policy#put-cluster-policy) REST API request:\n\n    [code example]"
    },
    {
      "id": "database-version",
      "title": "Database version",
      "role": "content",
      "text": "New databases use the default Redis database version unless you select a different **Database version** when you [create a database](https://redis.io/docs/latest/operate/rs/databases/create) in the Cluster Manager UI or specify the `redis_version` in a [create database REST API request](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/bdbs).\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](https://redis.io/docs/latest/operate/rs/references/cli-utilities/rladmin/tune#tune-cluster): \n    \n    [code example]\n\n- [Update cluster policy](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/cluster/policy#put-cluster-policy) REST API request:\n\n    [code example]"
    },
    {
      "id": "internode-encryption",
      "title": "Internode encryption",
      "role": "content",
      "text": "Enable [internode encryption](https://redis.io/docs/latest/operate/rs/security/encryption/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](https://redis.io/docs/latest/operate/rs/references/cli-utilities/rladmin/tune#tune-cluster): \n    \n    [code example]\n\n- [Update cluster policy](https://redis.io/docs/latest/operate/rs/references/rest-api/requests/cluster/policy#put-cluster-policy) REST API request:\n\n    [code example]"
    }
  ],
  "examples": [
    {
      "id": "database-proxy-ex0",
      "language": "sh",
      "code": "rladmin tune cluster default_non_sharded_proxy_policy { single | all-master-shards | all-nodes }",
      "section_id": "database-proxy"
    },
    {
      "id": "database-proxy-ex1",
      "language": "sh",
      "code": "PUT /v1/cluster/policy \n    { \"default_non_sharded_proxy_policy\": \"single | all-master-shards | all-nodes\" }",
      "section_id": "database-proxy"
    },
    {
      "id": "database-proxy-ex2",
      "language": "sh",
      "code": "rladmin tune cluster default_sharded_proxy_policy { single | all-master-shards | all-nodes }",
      "section_id": "database-proxy"
    },
    {
      "id": "database-proxy-ex3",
      "language": "sh",
      "code": "PUT /v1/cluster/policy \n    { \"default_sharded_proxy_policy\": \"single | all-master-shards | all-nodes\" }",
      "section_id": "database-proxy"
    },
    {
      "id": "shards-placement-ex0",
      "language": "sh",
      "code": "rladmin tune cluster default_shards_placement { dense | sparse }",
      "section_id": "shards-placement"
    },
    {
      "id": "shards-placement-ex1",
      "language": "sh",
      "code": "PUT /v1/cluster/policy \n    { \"default_shards_placement\": \"dense | sparse\" }",
      "section_id": "shards-placement"
    },
    {
      "id": "database-version-ex0",
      "language": "sh",
      "code": "rladmin tune cluster default_redis_version <x.y>",
      "section_id": "database-version"
    },
    {
      "id": "database-version-ex1",
      "language": "sh",
      "code": "PUT /v1/cluster/policy \n    { \"default_provisioned_redis_version\": \"x.y\" }",
      "section_id": "database-version"
    },
    {
      "id": "internode-encryption-ex0",
      "language": "sh",
      "code": "rladmin tune cluster data_internode_encryption { enabled | disabled }",
      "section_id": "internode-encryption"
    },
    {
      "id": "internode-encryption-ex1",
      "language": "sh",
      "code": "PUT /v1/cluster/policy \n    { \"data_internode_encryption\": <boolean> }",
      "section_id": "internode-encryption"
    }
  ]
}