Help Center > > User Guide> Buying a DCS Instance> Buying a DCS Redis Instance

Buying a DCS Redis Instance

Updated at: Mar 17, 2020 GMT+08:00

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

Buying a DCS Redis Instance

  1. Log in to the DCS console.
  2. Click in the upper left corner of the management console and select a region and a project.

    Select the same region as your application service.

  3. Click Buy DCS Instance.
  4. Specify Billing Mode.
  5. Select a region closest to your application to reduce latency and accelerate access.
  6. Specify the following instance parameters based on the information collected in Identifying Requirements.

    1. Cache Engine:

      Select Redis.

    2. Version:

      Currently, 3.0, 4.0, and 5.0 versions are supported.

      • If Instance Type if set to Proxy Cluster, you can only select 3.0 for Version.
      • If Instance Type if set to Redis Cluster, you can only select 4.0 or 5.0 for Version.
    3. Set Instance Type to Single-node, Master/Standby, Proxy Cluster or Redis Cluster.
    4. Select an AZ.

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

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

    5. Edition: By default, Standard is selected.
    6. Instance Specification:

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

      Figure 1 shows the instance parameter settings.

      Figure 1 Buying a DCS Redis instance

  7. Configure the instance network parameters.

    1. For VPC, select a created VPC, subnet, and specify the IP address.

      If the Version is 4.0 or 5.0, the IP address will be automatically assigned. 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.

      If you selected 3.0 for Version, you can choose to obtain an automatically assigned IP address or manually specify an IP address that is available in the selected subnet. The port cannot be customized. Port 6379 will be used.

    2. 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 Redis 3.0 versions. DCS for Redis 4.0 and 5.0 are based on VPC endpoints and do not support security groups.

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

  8. 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, you must select the password-protected mode and set a password.
      • 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.

      For details about password complexity requirements, see DCS Password Complexity Requirements.

  9. Specify the required duration and quantity.

    After enabling public access, you can only create one DCS Redis instance at time.

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

    1. Specify Name and Description.

      When you create only one instance at a time, the value of Name must be a string consisting of 4 to 64 characters. When you create more than one instance at a time, the value of Name must be a string consisting of 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.

    2. Configure public access.

      You can enable or disable public access. Currently, only DCS Redis 3.0 instances support public access.

      • A DCS Redis instance with public access enabled is accessed using an EIP. After you enable public access, Elastic IP Address and SSL are displayed. Select an EIP. Click View Elastic IP to view or create EIPs.
      • SSL: An indicator of whether to enable SSL encryption during public access to your DCS Redis instance.

        When public access is enabled, SSL is enabled by default. This parameter cannot be modified once the instance is created with public access enabled.

        If you want to change the SSL setting after the instance is created, disable public access first to change the SSL setting.

    3. Specify Enterprise Project.
    4. Specify backup and restoration policies.

      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 Backing Up and Restoring Instances.

    5. Rename critical commands.

      Command Renaming is displayed for Redis 4.0 and 5.0. Currently, you can only rename the COMMAND, KEYS, FLUSHDB, FLUSHALL, and HGETALL commands.

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

    7. 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, use, owner, or environment).

      • 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 or create predefined tags.
      • You can also create new tags by specifying Tag key and Tag value.

      Up to 10 tags can be added to each DCS instance. For details about the requirements on tags, see Managing Tags.

  11. Click Next.

    The displayed page shows the instance information you have specified.

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

    1. Creating a single-node or master/standby DCS standard Redis instance takes 5 to 15 minutes. Creating a cluster DCS standard Redis instance takes 30 minutes.
    2. After a DCS instance has been successfully created, it enters the Running state by default.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel