Creating a DCS Redis Instance

Prerequisites

You have prepared necessary resources.

Creating a DCS Redis Instance

1. Log in to the DCS console.
2. Click in the upper left corner of the console and select a region and a project.
3. Click Buy DCS Instance.
4. Select a region closest to your application to reduce latency and accelerate access.
5. Select a project. By default, each region corresponds to a project.
6. Specify the following instance parameters based on the information collected in Identifying Requirements.
   1. In Cache Engine, select an engine. Default: Redis.
   2. Edition: Basic is available.
   3. CPU Architecture: x86 is available.
   4. Version:

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

      

      • To compare Redis versions, see Open Source Redis Versions.
      • 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.
   5. Set Instance Type to Single-node, Master/Standby, or Redis Cluster.
   6. Select an AZ as required.
      Instances other than single-node ones support both Primary AZ and Standby AZ.

      

      • If instance nodes in an AZ are faulty, nodes in other AZs will not be affected. The standby node automatically becomes the master node to continue to operate, ensuring disaster recovery (DR).
      • Deploying a DCS instance across AZs slightly reduces network efficiency compared with deploying an instance within an AZ. Therefore, if a DCS instance is deployed across AZs, synchronization between master and standby cache nodes is slightly less efficient.
      • 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. Set Replicas. The default value is 2 (including the master).

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

   8. Instance Specification:

      The remaining quota is displayed on the console.

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

      Figure 1 Creating a DCS Redis instance
      

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

      DCS Redis 4.0 and later instances support automatic IP address assignment and port customization. You can specify a port in the range from 1 to 65535. The default port is 6379.

   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.

      DCS for Redis 4.0 and later are based on VPC Endpoint and do not support security groups. Configure the whitelist after creating such an instance by referring to Managing IP Address Whitelist.

8. Enter an instance name and select an enterprise project.

   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.

9. Set the instance password.
   • Select Yes or No for Password Protected.
     

     • Password-free access carries security risks. Exercise caution when selecting this mode.
     • After creating a DCS Redis instance to be accessed in password-free mode, you can set a password for it by using the password reset function. 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.

10. Click Advanced Settings and set the following information as required.
    1. Configure Parameter Configuration. Retain Default templates or select Use custom template as required.

       If you select Use custom template, select one from the drop-down list box. To view or modify the configuration in the selected template, click View Parameter. If no custom parameter template of the selected instance version and type is available, the selection box is empty. In this case, click View Parameter Templates to go to the template creation page to create a template. For details, see Creating a Custom Parameter Template.

    2. To configure instance backup policies, 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.

    3. Cannot be configured during instance creation.
    4. Specify tags.

       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 tag naming requirements, see Managing Tags.
    5. 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.

    6. Enter a description of the instance.

11. Specify the number of instances to create.
12. Click Next.

    The displayed page shows the instance information you have specified.

13. Confirm the instance information and click Submit.
14. Return to the Cache Manager page to view and manage your DCS instances.
    1. 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.