[Yandex Cloud documentation](../../index.md) > [Yandex Managed Service for Valkey™](../index.md) > [Step-by-step guides](index.md) > Clusters > Creating a cluster # Creating a Valkey™ cluster A Valkey™ cluster consists of one or more database hosts, with the option to configure replication between them. Replication is enabled by default in any cluster with more than one host: the master host accepts write requests and propagates the changes to its replicas. For more information on the Yandex Managed Service for Valkey™ cluster structure, see [Resource relationships](../concepts/index.md). {% note info %} * The number of hosts you can create together with a Valkey™ cluster depends on the selected [disk type](../concepts/storage.md#storage-type-selection) and [host class](../concepts/instance-types.md#available-flavors), as well as on whether [sharding](../concepts/sharding.md) is used. * The available disk types [depend](../concepts/storage.md) on the selected [host class](../concepts/instance-types.md). {% endnote %} Cluster DB connections are managed by Connection Manager. Creating a cluster automatically creates: * [Connection Manager connection](../../metadata-hub/concepts/connection-manager.md) with information about the database connection. * [Yandex Lockbox secret](../../metadata-hub/concepts/secret.md) that stores the DB owner's user password. Storing passwords in Yandex Lockbox ensures their security. The connection and secret will be created for each new database user. To view all connections, select the **Connections** tab on the cluster page. You need the `connection-manager.viewer` role to view connection info. You can [use Connection Manager](../../metadata-hub/operations/connection-access.md) to configure access to connections. You can use Connection Manager and secrets you create there free of charge. ## Creating a cluster {#create-cluster} To create a Yandex Managed Service for Valkey™ cluster, you need the [vpc.user](../../vpc/security/index.md#vpc-user) role along with the [managed-redis.editor role or higher](../security/index.md#roles-list). To learn how to assign a role, see [this Identity and Access Management guide](../../iam/operations/roles/grant.md). {% note info %} The following restrictions apply when creating sharded clusters: * You can create a single-shard cluster using the CLI, Terraform, or API. * You cannot create a cluster with two shards, but you can [add a shard](shards.md#add) to an existing single-shard cluster. * You can create a cluster with three or more shards using the management console, CLI, Terraform, or API. There are no restrictions for non-sharded clusters. {% endnote %} {% list tabs group=instructions %} - Management console {#console} To create a Yandex Managed Service for Valkey™ cluster: 1. In the [management console](https://console.yandex.cloud), go to the folder where you want to create your database cluster. 1. Navigate to **Yandex Managed Service for Valkey™**. 1. Click **Create cluster**. 1. Under **Basic parameters**: * Enter a name for the cluster in the **Cluster name** field. The cluster name must be unique within the folder. * Optionally, add a cluster description. * Select your cluster environment. Note that you cannot change the environment once the cluster is created: * `PRODUCTION`: For stable versions of your applications. * `PRESTABLE`: For testing purposes. The prestable environment is similar to the production environment and likewise covered by an SLA, but it is the first to get new features, improvements, and bug fixes. In the prestable environment, you can test new versions for compatibility with your application. * Select the DBMS version. * Optionally, add labels. * Enable [cluster sharding](../concepts/sharding.md), if required. {% note warning %} You cannot disable sharding in a cluster where it is already enabled. You can create a non-sharded cluster and [enable sharding](update.md#enable-sharding) later, if required. {% endnote %} * Enable encrypted TLS connections to your cluster, if required. {% note warning %} You can enable encrypted connections only when creating a new cluster. You cannot disable encryption for an existing cluster. {% endnote %} * Optionally, enable [using FQDNs instead of IP addresses](../concepts/network.md#fqdn-ip-setting). {% note info %} Some clients do not support this setting and will fail to connect to the cluster hosts. They expect an IP address and will produce errors if you provide an FQDN instead. {% endnote %} * Select the [data persistence](../concepts/replication.md#persistence) mode. 1. Under **Resources**: * Select a platform in the **Platform** field. * Specify the **Type** of virtual machine where you want to deploy the hosts. * Select **Host class**. * Select the [disk type](../concepts/storage.md): * Either the more flexible network SSD (`network-ssd`) or non-replicated SSD (`network-ssd-nonreplicated`) storage * Or the faster local SSD (`local-ssd`) storage The type you select determines the increments for changing the disk size: * Network SSD storage: In increments of 1 GB. * Local SSDs: * For **Intel Broadwell** and **Intel Cascade Lake**: In 100 GB increments. * For **Intel Ice Lake** and **AMD Zen 4**: In 368 GB increments. * Non-replicated SSDs: In increments of 93 GB. * Select the storage size. The available storage size is capped by [quotas and limits](../concepts/limits.md#mrd-limits). * In the **Increase size** field, set the conditions for the actions below: * Storage expansion during the [next maintenance window](../concepts/maintenance.md#maintenance-window) if and when the specified storage space utilization percentage is exceeded. If you set this condition, configure the maintenance schedule. * Storage expansion immediately if and when the specified storage space utilization percentage is exceeded. {% note warning %} If you set both conditions, make sure the immediate expansion threshold is higher than the scheduled one. {% endnote %} * In the **Maximum storage size** field, specify the maximum storage size that can be set during autoscaling. {% note warning %} * You cannot decrease the storage size after automatic expansion. * During storage resizing, cluster hosts will be stopped and updated one at a time. {% endnote %} * Optionally, select **Encrypted disk** to encrypt the disk with a [custom KMS key](../../kms/concepts/key.md). * To [create](../../kms/operations/key.md#create) a new key, click **Create**. * To use a previously created key, select it in the **KMS key** field. To learn more about disk encryption, see [Storage](../concepts/storage.md#disk-encryption). 1. Under **Network settings**, select: * [Cloud network](../../vpc/concepts/network.md#network) for cluster deployment. * Security groups for cluster network traffic. You may need to additionally [set up security groups](connect/index.md#configuring-security-groups) to be able connect to the cluster. 1. Under **Hosts**, configure the hosts: * To change the settings of a host, click ![pencil](../../_assets/console-icons/pencil.svg) next to the host name. * **Availability zone**: Select the [availability zone](../../overview/concepts/geo-scope.md). * **Subnet**: Specify a [subnet](../../vpc/concepts/network.md#subnet) in the selected availability zone. * **Public access**: Enables access to the host from the internet if you enabled **TLS support** for the cluster. * **Master priority**: Host priority for promotion to master if the [primary master fails](../concepts/replication.md#master-failover). * **Shard name**: Enables you to change the shard name for the host. This field is only available if you enabled **Cluster sharding** for the cluster. * To add hosts to your cluster, click **Add host**. If you enabled cluster sharding and selected the **local-ssd** disk type, add at least two hosts per shard. 1. Under **DBMS settings**: * In the **Password** field, enter the user password. The password must be from 8 to 128 characters long and match the `[a-zA-Z0-9@=+?*.,!&#$^<>_-]*` regular expression. * Configure the [DBMS settings](../concepts/settings-list.md), if required. 1. Under **Service settings**, configure the additional cluster settings as follows: - **Backup start time (UTC)**: Cluster backup start time (UTC, 24-hour format). If you leave the time unset, the [backup](cluster-backups.md) will start at 22:00 UTC. - **Maintenance**: [Maintenance window](../concepts/maintenance.md) settings: * To enable maintenance at any time, select **At any time** (default). * To specify the preferred maintenance start time, select **By schedule** and specify the day of the week and the UTC time interval. For example, you can choose a time when the cluster is least loaded. Both active and stopped clusters are subject to maintenance. Maintenance operations include DBMS updates, patches, etc. - **Deletion protection**: Manages cluster protection against accidental deletion. Even with deletion protection enabled, one can still connect to the cluster manually and delete the data. - **WebSQL access**: This option enables you to [run SQL queries](web-sql-query.md) against cluster databases from the Yandex Cloud management console using Yandex WebSQL. 1. Under **Modules**, enable the required [Valkey™ modules](../concepts/modules.md). For the **Search** module, configure the following settings: **Number of reader threads** and **Number of writer threads**. {% note warning %} You cannot disable modules once enabled. {% endnote %} 1. Click **Create cluster**. - CLI {#cli} If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install). The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id ` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions. To create a Yandex Managed Service for Valkey™ cluster: 1. Check whether the folder has any subnets for cluster hosts: ```bash yc vpc subnet list ``` If there are no subnets in the folder, [create the right ones](../../vpc/operations/subnet-create.md) in VPC. 1. View the description of the CLI command for creating a cluster: ```bash yc managed-redis cluster create --help ``` 1. When creating a cluster with the CLI, you cannot explicitly specify the host type and RAM size. Select the appropriate [host class](../concepts/instance-types.md) instead. To view the available host classes, run the following command: ```bash yc managed-redis resource-preset list ``` 1. Run this command, providing the cluster settings (our example lists only some flags): ```bash yc managed-redis cluster create \ --name \ --environment \ --redis-version \ --network-name \ --host zone-id=,` `subnet-id=,` `assign-public-ip=,` `replica-priority= \ --security-group-ids \ --enable-tls \ --persistence-mode \ --resource-preset \ --disk-size \ --disk-size-autoscaling disk-size-limit=,` `planned-usage-threshold=,` `emergency-usage-threshold= \ --disk-type-id \ --password= \ --backup-window-start