Updated on 2024-03-04 GMT+08:00

Buying a DCS Redis Instance

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

  • DCS for Redis 3.0 is no longer provided. This section only describes how to create a DCS Redis 4.0 or later instance.
  • Currently, DCS for Redis 6.0 is available only in some regions, such as CN North-Beijing4 and CN South-Guangzhou.
  • The supported Redis versions and instance types vary across regions.


  • To achieve fine-grained management of your HUAWEI CLOUD resources, create IAM user groups and users and grant specified permissions to the users. For details, see Permission Management.
  • You have prepared necessary resources.


  1. Go to the Buy DCS Instance page.
  2. Specify Billing Mode.
  3. Select a region closest to your application to reduce latency and accelerate access.
  4. Set the following information:

    1. Cache Engine: The default engine is Redis.
    2. Edition: The default edition is Basic.

      Professional (performance) and Professional (storage) are supported only when Version is set to 6.0. Learn more about Redis 6.0 Instance Specifications and Redis 6.0 Commands.

    3. CPU Architecture: x86 and Arm are available. x86 is recommended. Arm is unavailable in some regions.
    4. Version:

      Currently supported Redis versions: 4.0/5.0/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.
    5. Instance Type: Options include Single-node, Master/Standby, Read/Write splitting, Proxy Cluster, and Redis Cluster.
    6. Replicas: The default value is 2.

      This parameter is displayed only when the instance type is master/standby, read/write splitting, or Redis Cluster.

    7. If Proxy Cluster or Redis Cluster is selected, the Sharding parameter is displayed.

      Use default: Use the default sharding specifications.

      Customize: Customize the size of each shard and then select corresponding instance specifications.

    8. Select an AZ.

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

      If the instance type is master/standby, read/write splitting, Proxy Cluster, or Redis Cluster, AZ becomes Primary AZ, and Standby AZ is displayed. Select an AZ for the master and standby nodes of the instance.

    9. Instance Specification:

      The default quota is displayed on the console.

      To increase quota, click Increase quota below the specifications. On the displayed page, fill in a quota application form and click Submit.

      The instance parameter settings are shown in the following figure.

      Figure 1 Buying a DCS Redis instance

  5. 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 a private IP address for your instance as required.

      For basic edition Redis instances, you can specify a port numbering in the range from 1 to 65535. If no port is specified, the default port 6379 will be used.

      For Redis 6.0 professional, you cannot customize a port. The default 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.

      Only professional edition Redis instances require security groups. Basic edition DCS Redis instances are based on VPC endpoints and do not support security groups. To control access to these instances, configure a whitelist after the instances are created.

      If port 6379 is not enabled for the selected security group, the Enable port 6379 check box is displayed and selected by default, indicating that after the instance is created, port 6379 will be enabled for the selected security group. If port 6379 is not enabled for the selected security group, connections to the instance may fail.

      Figure 2 Configuring instance network parameters

  6. Set the instance password.

    • Select Yes or No for Password Protected.
      • Password-free access carries security risks. Exercise caution when selecting this mode.
      • If you are to enable public access for a DCS Redis 3.0 instance, you must select the password-protected mode and set a password.
      • Even if you created a password-free DCS Redis instance, you can still set a password after the instance is created. For details, see Changing Password Settings for DCS Redis Instances.
    • 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.

  7. 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.

  8. Specify the required duration and instance quantity for yearly/monthly billing.
  9. Enter an instance name and select an enterprise project.

    When you create only one instance at a time, the value of Name can contain 4 to 64 characters. When you create more than one instance at a time, the value of Name can contain 4 to 56 characters. These instances are named in the format of "name-n", in which 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.

    If you cannot select an enterprise project, check your permissions. For details, see Why Can't I Select the Required Enterprise Project When Creating a DCS Instance?

  10. Click More Settings to display more configurations, including backup policy and critical command renaming.

    1. Enter a description of the instance.
    2. Specify the backup policy.

      This parameter is displayed only when the instance type is master/standby, read/write splitting, or cluster. For details about instance backup and backup policies, see Backing Up and Restoring Instances.

    3. Rename critical commands.

      Currently, you can only rename the COMMAND, KEYS, FLUSHDB, FLUSHALL, HGETALL, SCAN, HSCAN, SSCAN, and ZSCAN commands. For Proxy Cluster instances, you can also rename the DBSIZE and DBSTATS commands.

    4. 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.

    5. Add a tag.

      Tags are used to identify cloud resources. When you have many cloud resources of the same type, you can use tags to classify cloud resources by dimension (for example, by usage, owner, or environment).

      If tag policies for DCS have been set in your organization, add tags to DCS instances based on these policies. If a tag does not comply with the tag policies, DCS instance creation may fail. Contact your organization administrator to learn more about tag policies.

      • If you have created predefined tags, select a predefined pair of tag key and value. Click View predefined tags. On the Tag Management Service (TMS) console, view predefined tags or create new tags.
      • You can also add a tag by entering the tag key and value. For details about how to name tags, see Managing Tags.

  11. Click Next.

    The displayed page shows the instance information you have specified.

  12. Confirm the instance information and submit the request.
  13. Return to the Cache Manager page to view and manage your DCS instances.