Updated on 2025-09-26 GMT+08:00

Buying a GeminiDB Redis Cluster Instance

This section describes how to buy a GeminiDB Redis cluster instance on the GeminiDB console.

In a sharded cluster, a proxy cluster GeminiDB Redis instance is connected through proxies to a standalone Redis instance, Redis Sentinel, and Redis Cluster. The proxy cluster instance has strong horizontal scaling capabilities and can handle millions of QPS and dozens of terabytes of data.

Each tenant can create a maximum of 50 GeminiDB Redis instances by default. To request a higher quota, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service.

Prerequisites

  • You have created a Huawei Cloud account.

Procedure

  1. Log in to the GeminiDB console.
  2. On the Instances page, click Buy DB Instance.
  3. On the displayed page, specify instance specifications and click Next.

    Figure 1 Billing mode and basic information
    Table 1 Billing mode description

    Parameter

    Description

    Billing Mode

    Select Yearly/Monthly or Pay-per-use.

    • Yearly/Monthly
      • Specify Required Duration. The system deducts fees 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. For details, see Changing a Yearly/Monthly Instance to Pay-per-Use.
        NOTE:
        • Yearly/Monthly instances cannot be deleted directly. If such an instance is no longer required, unsubscribe from it. For details, see Unsubscribing a Yearly/Monthly Instance.
        • Yearly/Monthly instances with cloud native storage are now in OBT. To use such an instance, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service.
    • Pay-per-use
      • If you select this billing mode, you are billed based on how much time the instance is in use.
      • To use an instance for a long time, change its billing mode to yearly/monthly to reduce costs. For details, see Changing a Pay-per-Use Instance to Yearly/Monthly.
    Table 2 Basic information

    Parameter

    Description

    Region

    Region where a tenant is located

    NOTE:

    To reduce network latency, select a region nearest from which you will access the instance. 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 contain 4 to 64 characters 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 a GeminiDB Redis Instance Name.

    Compatible API

    Redis

    GeminiDB is compatible with mainstream NoSQL databases, including Redis, DynamoDB, Cassandra, and InfluxDB. You can select GeminiDB APIs by following How Do I Select an API?

    Storage Type

    • Classic: classic architecture with decoupled storage and compute
    • Cloud native: more flexible, new-gen version with support for more AZs
      NOTE:
      • Cloud native storage supports only proxy cluster instances.
      • Classic and cloud native are different deployment modes. Cloud native supports more AZs. If both classic and cloud native are supported, you can select any of them.

    Product Type

    Standard: Stable and low-latency performance is provided for common scenarios such as advertising and recommendation, gaming, e-commerce, and Internet of Vehicles (IoV).

    DB Instance Type

    Proxy cluster:

    In a sharded cluster, a proxy cluster GeminiDB Redis instance is connected through proxies to a standalone Redis instance, Redis Sentinel, and Redis Cluster. The proxy cluster instance has strong horizontal scaling capabilities and can handle millions of QPS and dozens of terabytes of data.

    NOTE:

    To create a Redis Cluster instance, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service to grant required permissions.

    Compatible Version

    7.0, 6.2 (including 6.2.X), 5.0, and earlier versions

    CPU Type

    x86

    x86 CPUs use the Complex Instruction Set Computing (CISC) instruction set. Each instruction can be used to execute low-level hardware operations. Executing these instructions is complex and time-consuming.

    AZ

    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 with each other over a private network.

    Figure 2 Specifications and storage
    Table 3 Specifications and storage

    Parameter

    Description

    Instance Creation Method

    Two options are available:

    • Fast configure

      Recommended specifications, node quantity, and storage space

      NOTE:
      • Instance specifications with the memory of 8 GB and 16 GB are available only in single AZs. The console shows available specifications.
      • The QPS is only for reference.

      Standard configure

      Instance flavor, node specifications, node quantity, and storage space that can be specified

    Instance Specifications

    You need to specify instance specifications after selecting Fast configure for Instance Creation Method.

    Higher CPU specifications provide better performance. Select specifications as needed.

    For details, see Instance Specifications.

    Specification Type

    You need to select a specification type after selecting Standard configure for Instance Creation Method.

    • Standard: The default and recommended CPU-to-memory ratio is 1:4, which balances low latency demands with high concurrency requirements.
    • Enhanced: The CPU-to-memory ratio is 1:8, which boosts the access hit rate while reducing latency.

    Node Specifications

    You need to select node specifications after selecting Standard configure for Instance Creation Method and Classic for Storage Type.

    For details, see Instance Specifications.

    Nodes

    You need to specify the node quantity after selecting Standard configure for Instance Creation Method and Classic for Storage Type.

    Number of required nodes. After an instance is created, you can add nodes.

    Currently, a maximum of 36 nodes are supported. To add more, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service.

    Total Storage Space

    You need to specify the storage space after selecting Standard configure for Instance Creation Method.

    Higher CPU specifications provide better performance. Select specifications as needed.

    For details, see Instance Specifications.

    Specification Preview

    After you select instance specifications, the system automatically shows details of the total capacity, node specifications, number of nodes, QPS benchmark, total number of connections, and number of data copies. This helps keep track of the selected instance specifications.

    Table 4 Network

    Parameter

    Description

    VPC

    Virtual private network where your instances are located. 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.

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

    NOTE:
    • After a GeminiDB Redis instance is created, its VPC cannot be changed.
    • To connect a GeminiDB Redis instance to an ECS over a private network, ensure the GeminiDB Redis instance and the ECS are in the same VPC. If they are not, you can create a VPC peering connection between them.

    Subnet

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

    NOTE:

    An IPv6 subnet cannot be associated with your instance. Select an IPv4 subnet.

    Security Group

    A security group controls access between GeminiDB Redis instances and other services. Ensure that the security group you selected allows your client to access the instance.

    If no security group is available, the system creates one for you.

    Table 5 Database configuration

    Parameter

    Description

    Password

    • Skip: You can set the database password after creating an instance.
    • Configure: You can set the database password when creating an instance.

    Password

    Password of database administrator rwuser:

    • Must be 8 to 32 characters long.
    • Can contain at least two types of the following characters: 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 database password again.

    Table 6 Enterprise project

    Parameter

    Description

    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 projects, see Enterprise Management User Guide.

    Table 7 Advanced settings

    Parameter

    Description

    SSL

    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.

    NOTE:

    Tags

    This setting is optional. Adding tags helps you better identify and manage your instances. A maximum of 20 tags can be added for each instance.

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

    • A tag key is mandatory if the instance will be tagged.

      Each tag key is unique for each instance. It can contain 1 to 128 characters, cannot start with _sys_, and cannot start or end with a space. Only letters, digits, spaces, and the following special characters are allowed: -_@.:/+=

    • A tag value is optional if the instance will be tagged.

      The value can be empty.

      The value can contain a maximum of 255 characters. Only letters, digits, spaces, and the following special characters are allowed: _.-:+=@/

    After an 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 Tag Management.

    Table 8 Required duration

    Parameter

    Description

    Required Duration

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

    Auto-renew

    • By default, this option is not selected.
    • If you select this option, the instance is automatically renewed based on the subscription duration.

  4. On the displayed page, confirm instance details.

    • Yearly/Monthly
      • To modify the configurations, click Previous.
      • If no modification is required, read and agree to the service agreement, click Pay Now, and complete the payment.
    • Pay-per-use
      • To modify the configurations, click Previous.
      • If no modification is required, read and agree to the service agreement and click Submit.

  5. On the Instances page, view and manage the created instance.

    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.

    The default database port of the instance is 6379 and cannot be changed.