Updated on 2025-08-04 GMT+08:00

Buying a GeminiDB HBase Instance

This section describes how to buy a GeminiDB HBase instance.

GeminiDB Cassandra, DynamoDB-Compatible, and HBase instances of each tenant share a quota. Each tenant can create a maximum of 50 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.

Usage Notes

The default version of GeminiDB HBase is 3.11.

Procedure

  1. Log in to the Huawei Cloud console.
  2. On the Instances page, click .
  3. On the displayed page, select a billing mode, select HBase for Compatible API, configure information about your instance. Click Next.

    Figure 1 Billing mode and basic information (classic storage)
    Figure 2 Billing mode and basic information (cloud native storage)
    Table 1 Billing mode

    Parameter

    Description

    Billing Mode

    Select Yearly/Monthly or Pay-per-use.

    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 include 4 to 64 bytes and must start with a letter. It is case-sensitive and allows only letters, digits, hyphens (-), and underscores (_).

    Compatible API

    HBase

    GeminiDB is compatible with mainstream NoSQL APIs, including Redis, DynamoDB, Cassandra, HBase, MongoDB, 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:
    • The way you use instances with classic or cloud native storage is similar. Cloud native storage supports more AZs. If both classic and cloud native are supported, you can select any of them.
    • Cloud native storage is now in OBT. To use it, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service.

    DB Instance Type

    Cluster

    One cluster consists of at least three nodes. A cluster is easy to scale out to meet increasing data growth needs. A cluster is recommended when dealing with stringent availability demands, substantial data volumes, and the need for seamless scalability.

    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 3 Specifications and storage
    Table 3 Specifications and storage

    Parameter

    Description

    Instance Specifications

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

    Nodes

    The number of nodes ranges from 3 to 80.

    Storage Space

    Instance storage space. The range depends on the instance specifications.

    To scale up storage, you need to add at least 1 GB each time. The value must be an integer.

    Disk Encryption

    You can determine whether to encrypt disks.

    • Disable: Data is not encrypted.
    • Enable: Your data will be encrypted on disks and stored in ciphertext after you create an 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 I/O performance.
      • Key Name: Select an existing key or create one.
      NOTE:
      • This function is now in OBT. To use it, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service.
      • An agency will be created after disk encryption is enabled.
      • After an instance is created, the disk encryption status and key cannot be changed.
      • The key cannot be disabled, deleted, or frozen when used, or the database becomes unavailable.
      • For details about how to create a key, see "Creating a CMK" in Data Encryption Workshop User Guide.
    Figure 4 Network settings

    Table 4 Network settings

    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.

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

    For details, see "Creating a VPC" in the 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.

    NOTE:
    • 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.

    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 instances and other services. When you select a security group, you must ensure that it allows your client to access your instances.

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

    Figure 5 Database configuration

    Table 5 Database configuration

    Parameter

    Description

    Administrator

    The default administrator account is rwuser.

    Administrator Password

    Password of the administrator account. The password:

    • Must be 8 to 32 characters long.
    • Must contain uppercase letters, lowercase letters, digits, and any of the following special characters: ~!#%^*-_=+?
    • Cannot contain @ or /
    • 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.

    Parameter Template

    A parameter template contains engine configuration values that can be applied to one or more instances. You can modify the instance parameters as required after the DB instance is created.

    After an instance is created, you can change the parameter template based on service requirements.

    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 are advised to enable SSL connection to improve data security.

    NOTE:

    If SSL is not enabled when you create an instance, you can enable it after the instance is created. For details, see Encrypting Data over SSL for a GeminiDB Cassandra Instance.

    Table 6 Tags

    Parameter

    Description

    Tag

    Tags a instance. This parameter is optional. Adding tags helps you better identify and manage your instances.

    A maximum of 20 tags can be added for each instance.

    If your organization has configured a tag policy for , 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.

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

      Each tag key is unique for each instance. It can contain a maximum of 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 is going to 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: _.-:+=@/

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

    • 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 your instances.

    • The instance status is displayed as Creating.
    • After the instance is created, its status becomes Available.

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

    • An automated backup policy is enabled by default during instance creation. A full backup is automatically triggered after a DB instance is created.

    After the instance is created, Cassandra 3.11.3 is displayed in the Compatible API column on the Instances page and is compatible with HBase. The usage is the same as that of HBase.