Updated on 2024-05-30 GMT+08:00

Buying a DB Instance (Primary/Standby)

This section describes how to buy a primary/standby Redis instance that is compatible with the Redis API on the GeminiDB console.

Each tenant can have up to 50 GeminiDB Redis instances by default. To create more instances, contact customer service.


  • You have registered a Huawei Cloud account.


  1. Log in to the management console.
  2. In the service list, choose Databases > GeminiDB Redis API.
  3. On the Instance Management page, click Buy DB Instance.
  4. On the displayed page, select a billing mode, select instance specifications and click Next.

    Figure 1 Billing mode and basic information

    Table 1 Billing mode description



    Billing Mode

    Method that the instance is billed in. The value can be Yearly/Monthly or Pay-per-use.

    • Yearly/Monthly
      • In this mode, specify Required Duration at the bottom of the page. The system deducts the fees incurred from your account based on the service price.
      • If you do not need such an instance any longer after it expires, change the billing mode to pay-per-use to optimize costs. For details, see Changing the Billing Mode from Yearly/Monthly to Pay-per-Use.

        Yearly/Monthly instances cannot be deleted directly. If such an instance is no longer required, unsubscribe from it. For details, see Unsubscribing from a Yearly/Monthly Instance.

    • Pay-per-Use Billing
    Table 2 Basic information




    The region where the tenant is located.


    To reduce network latency, deploy your instance in the region nearest to your workloads. Instances deployed in different regions cannot communicate with each other over a private network. After you buy an instance, you cannot change its region.

    DB Instance Name

    The instance name:

    • Can be the same as an existing instance name.
    • Can include 4 to 64 bytes and must start with a letter. It is case-sensitive and allows only letters, digits, hyphens (-), and underscores (_).

    You can change the name of an instance after it is created. For details, see Modifying the Name of an Instance.

    Compatible API


    DB Instance Type


    With a standard primary/standby architecture, this type of instance is compatible with single-node instances and supports connecting to the sentinel node. This instance applies to service scenarios where hash tags cannot be used.

    Compatible Version

    5.0 or earlier.


    Availability zone where the instance is created. An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network. AZs are classified into primary AZs and secondary AZs.

    Instances can be deployed in a single AZ or three AZs.

    • If low network latency is required, deploy your instance in one AZ.
    • If disaster recovery is required, select three AZs and select the primary AZ and secondary AZs as required.
      • Primary AZ : the AZ where the primary node is located.
      • Standby AZ: the AZ where the standby node is located.
    Figure 2 Specifications and storage

    Table 3 Specifications and storage



    Instance Specifications

    Larger vCPU specifications can provide better performance. Select specifications based on your service requirements.

    For details, see Instance Specifications.

    Static Data Encryption

    You can select to enable disk encryption based on service requirements.

    • Disabled: Data storage is not encrypted.
    • Enabled: Data store is encrypted. If you select this option, your data will be encrypted on disks and stored in ciphertext after you create a DB instance. When you download encrypted objects, the ciphertext will be decrypted into plain text and then sent to you. Disk encryption can improve data security and may have slight impacts on database writes and reads.

      Key Name: Select an existing key or create one.

      • This function is in the open beta test (OBT) phase. To use this function, contact customer service.
      • An agency will be created after disk encryption is enabled.
      • After an instance is created, the disk encryption status and the key cannot be changed.
      • The key cannot be disabled, deleted, or frozen when it is in use. Otherwise, the database becomes unavailable.
      • For details about how to create a key, see "Creating a Key" in Data Encryption Workshop User Guide.

    Load Balancer IP Address

    This option is selected by default and cannot be changed.

    After an instance is created, you can use the load balancer address to connect to the instance. For details, see Connecting to an Instance Using a Load Balancer Address (Recommended).

    Table 4 Network




    The virtual network where the instance is created. A VPC isolates networks for different services. You can select an existing VPC or create a VPC.

    For details about how to create a VPC, see "Creating a VPC" in Virtual Private Cloud User Guide.

    With VPC sharing, you can also use a VPC and subnet shared by another account.

    VPC owners can share the subnets in a VPC with one or multiple accounts through Resource Access Manager (RAM). This allows for more efficient use of network resources and reduces O&M costs.

    For more information about VPC subnet sharing, see VPC Sharing in the Virtual Private Cloud User Guide.

    If there are no VPCs available, the system allocates resources to you by default.

    • After an instance is created, the VPC where the instance is deployed cannot be changed.
    • If you want to connect to an instance using an ECS over a private network, ensure that the instance and the ECS are in the same VPC. If they are not, create a VPC peering connection between them for access.


    A subnet where your instance is created. The subnet provides dedicated and isolated networks, improving network security.


    IPv6 subnets are not supported. You are advised to create and select IPv4 subnets.

    Security Group

    A security group controls access between instances and other services. Ensure that the security group you select allows the client to access the DB instance.

    If there are no security groups available, the system allocates resources to you by default.


    A security protocol. Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission.

    You can enable SSL to improve data security. After an instance is created, you can connect to it using SSL.


    If SSL is not enabled when you create an instance, you can enable it after the instance is created. For details, see Configuring an SSL Connection.

    Database Port

    Port number for accessing the instance.

    You can specify a port number based on your requirements. The port number ranges from 1024 to 65535 except 2180, 2887, 3887, 6377, 6378, 6380, 8018, 8079, 8091, 8479, 8484, 8999, 12017, 12333, and 50069.

    If you do not specify a port number, port 6379 is used by default.

    If you want to use this instance for dual-active DR, set the port to 8635.


    You cannot change the database port after an instance is created.

    Figure 3 Database configuration

    Table 5 Database configuration



    Database Password

    Password of the administrator account. The password:

    • Must be 8 to 32 characters long.
    • Can include two of the following: uppercase letters, lowercase letters, digits, and special characters: ~!@#$%^&*()-_=+?$()&
    • For security reasons, set a strong password. The system will verify the password strength.

    Keep your password secure. The system cannot retrieve it if it is lost.

    Confirm Password

    Enter the administrator password again.

    Enterprise project

    This parameter is provided for enterprise users.

    An enterprise project groups cloud resources, so you can manage resources and members by project. The default project is default.

    Select an enterprise project from the drop-down list. For more information about enterprise project, see Enterprise Management User Guide.

    Table 6 Password-free access configuration



    Password-Free Access

    Configure password-free access for a CIDR Block of the instance you want to access. After that, the password is not required the instance access.

    • Skip

      If you select Skip, you can set password-free access after the GeminiDB Redis instance is created. For details, see Enabling Password-Free Access.

    • Configure

      Enter a CIDR block that you want to enable password-free access for. A maximum of 30 password-free CIDR blocks can be configured.

    Table 7 Tag




    The setting is optional. Adding tags helps you better identify and manage your instances. Each instance supports up to 20 tags by default. To use more tags, contact customer service to apply for a quota of 20 tags.

    If your organization has configured a tag policy for GeminiDB Redis, you need to add a tag to the instance based on the tag policy. If the tag does not comply with the tag policy, the instance may fail to be created. Contact the organization administrator to learn details about the tag policy.

    A tag consists of a tag key and a tag value.

    • Tag key: Mandatory if the instance is going to be tagged.

      Each tag key must be unique for each instance. The key can include up to 36 characters, including digits, letters, underscores (_), and hyphens (-).

    • Tag value: Optional if the instance is going to be tagged.

      The value can contain up to 43 characters, including digits, letters, underscores (_), periods (.), and hyphens (-).

    After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags of an existing instance. For details, see Managing Tags.

    Table 8 Required duration



    Required duration

    The length of your subscription if you select Yearly/Monthly billing. Subscription lengths range from one month to three years.

    Auto-renewing an Instance

    • By default, this option is not selected.
    • If you select this option, the auto-renew cycle is determined by the selected required duration.

  5. On the displayed page, confirm the instance details.

    • Yearly/Monthly Billing
      • If you need to modify the settings, click Previous.
      • If you do not need to modify the settings, read and agree to the service agreement and click Pay Now to go to the payment page and complete the payment.
    • Pay-per-Use Billing
      • If you need to modify the settings, click Previous.
      • If no modification is required, read and agree to the service agreement and click Submit.

  6. On the Instances page, view and manage your instances.

    The instance creation process takes about 5 to 15 minutes. After the creation is complete, the status changes to Available.

    You can click in the upper right corner of the page to refresh the instance status.