Creating a DCS Redis Instance

You can create one or more DCS Redis instances with the required computing capabilities and storage space based on service requirements.


The system automatically schedules the task every 3 minutes for checking whether resources are available or sold out.


You have prepared necessary resources.

Creating a DCS Redis Instance

  1. Log in to the DCS console.

  2. Click image1 in the upper left corner of the management console and select a region and a project.

  3. Click Create DCS Instance.

  4. Select a region closest to your application to reduce latency and accelerate access.

  5. Specify the following instance parameters based on the information collected in Identifying Requirements.

    1. Cache Engine:

      Select Redis.

    2. Version:

      Currently, versions 3.0/4.0/5.0/6.0 are supported.


      • When creating a Proxy Cluster instance, you can only select version 3.0.

      • When creating a Redis Cluster instance, you can select versions 4.0, 5.0, or 6.0.

      • The Redis version cannot be changed once the instance is created. To use a later Redis version, create another DCS Redis instance and then migrate data from the old instance to the new one.

      • The method of connecting a client to a Redis Cluster instance is different from that of connecting a client to other types of instances. For details, see Accessing a DCS Redis Instance Through redis-cli.

    3. Set Instance Type to Single-node, Master/Standby, Proxy Cluster or Redis Cluster.

    4. Set CPU Architecture to x86.

    5. Set Replicas. The default value is 2 (including the master).

      This parameter is displayed only when you select Redis 4.0/5.0/6.0 and the instance type is master/standby or Redis Cluster.

    6. Select an AZ.

      If the instance type is master/standby, Proxy Cluster, or Redis Cluster, Standby AZ is displayed. Select a standby AZ for the standby node of the instance.


      • To accelerate access, deploy your instance and your application in the same AZ.

      • There are multiple AZs in each region. If resources are insufficient in an AZ, the AZ will be unavailable. In this case, select another AZ.

    7. Instance Specification:

      The remaining quota is displayed on the console.

      To apply to increase quota, click Increase quota below the specifications.

  6. Configure the instance network parameters.

    1. Select a VPC and a subnet.

    2. Configure the IP address.

      Redis Cluster instances only support automatically-assigned IP addresses. The other instance types support both automatically-assigned IP addresses and manually-specified IP addresses. You can manually specify an IP address available in your subnet.

      For a DCS Redis 4.0 or later instance, you can specify a port number in the range from 1 to 65535. If no port is specified, the default port 6379 will be used. For a DCS Redis 3.0 instance, the port cannot be customized. Port 6379 will be used.

    3. Select a security group.

      A security group is a set of rules that control access to ECSs. It provides access policies for mutually trusted ECSs with the same security protection requirements in the same VPC.

      This parameter is displayed only for DCS Redis 3.0 instances. DCS Redis 4.0/5.0/6.0 instances are based on VPC endpoints and do not support security groups. To control access to a DCS Redis 4.0/5.0/6.0 instance, configure a whitelist after instance creation. For details, see Managing IP Address Whitelist.

  7. Set the instance password.

    • Select Yes or No for Password Protected.


      • Password-free access carries security risks. Exercise caution when selecting this mode.

    • Password and Confirm Password: These parameters indicate the password of accessing the DCS Redis instance, and are displayed only when Password Protected is set to Yes.


      For security purposes, if password-free access is disabled, the system prompts you to enter an instance-specific password when you are accessing the DCS Redis instance. Keep your instance password secure and change it periodically.

  8. Configure Parameter Configuration.

    You can select Default Templates or Use custom template.


    • On the instance creation page, the default parameter templates are used by default.

    • If you use a custom template, the selected cache engine version and instance type must match those of the template. For details about using custom templates, see Creating a Custom Parameter Template.

  9. Choose whether to enable Auto Backup.

    This parameter is displayed only when the instance type is master/standby or cluster. For more information on how to configure a backup policy, see Overview.

  10. Specify the number of instances to create.

  11. Enter an instance name.

    The value of Name contains at least 4 characters. When you create multiple instances at a time, the instances are named in the format of custom name-n, where n starts from 000 and is incremented by 1. For example, if you create two instances and set name to dcs_demo, the two instances are respectively named as dcs_demo-000 and dcs_demo-001.

  12. Click More Settings to configure more parameters.

    1. Enter a description of the instance.

    2. Rename critical commands.

      Command Renaming is displayed for Redis 4.0 and later. Currently, you can only rename the COMMAND, KEYS, FLUSHDB, FLUSHALL, HGETALL, SCAN, HSCAN, SSCAN, and ZSCAN commands.

    3. Specify the maintenance window.

      Choose a window for DCS O&M personnel to perform maintenance on your instance. You will be contacted before any maintenance activities are performed.

  13. Click Create Now.

    The displayed page shows the instance information you have specified.

  14. Confirm the instance information and click Submit.

  15. Return to the Cache Manager page to view and manage your DCS instances.

    1. Creating a single-node or master/standby DCS Redis 3.0 instance takes 5 to 15 minutes. Creating a cluster DCS Redis 3.0 instance takes 30 minutes.DCS Redis 4.0 and later instances are containerized and can be created within seconds.

    2. After a DCS instance has been successfully created, it enters the Running state by default.


    • If the new DCS instance failed to be created, delete the unsuccessful instance creation task by following the procedure in Deleting Instance Creation Tasks That Have Failed to Run. Then, create the DCS instance again. If the DCS instance still fails to be created, contact customer service.

    • There is the management plane and the tenant plane. The tenant plane is also called the pod zone. During the creation of a DCS instance, a VM is created in the pod zone. If the instance creation fails, the instance status changes to Faulty, and the error message "Failed to connect to the instance. Network exceptions may have occurred in the pod zone." is displayed, indicating that the management plane cannot be connected to the tenant plane.