Buying a GeminiDB HBase Instance

Prerequisites

• You have created a Huawei Cloud account.

Procedure

1. Log in to the management 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
   

   Table 1 Billing mode

   Parameter	Description
   Billing Mode	Only pay-per-use billing mode is supported. If you select this billing mode, you are billed based on how much time the instance is in use.

   Table 2 Basic information

   Parameter	Description
   Region	The region where the tenant is located. NOTICE: 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 (_).
   Compatible API	HBase
   DB Instance Type	Cluster
   Version	3.11
   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 through an internal network.

   Figure 2 Specifications and storage
   

   Table 3 Specifications and storage

   Parameter	Description
   Instance Specifications	Larger vCPU specifications can provide better performance. Select specifications based on your service requirements.
   Nodes	The number of nodes ranges from 3 to 21. Specify nodes based on service requirements.
   Storage Space	Instance storage space. The range depends on the instance specifications. Select at least 1 GB each time you scale up the storage, and ensure that the increment is an integer.

   Figure 3 Network settings
   

   Table 4 Network settings

   Parameter	Description
   VPC	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. 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: 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. 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 4 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: ~!@#%^*-_=+? 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 Configuring an SSL Connection.

   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. Tag key: Mandatory if the instance is going to be tagged. Each tag key must be unique for each instance. The value can contain a maximum of 128 characters, including digits (0-9), letters, underscores (_), periods (.), hyphens (-), and Chinese characters. Tag value: Optional if the instance is going to be tagged. The value can contain a maximum of 255 characters, including digits (0-9), letters, underscores (_), periods (.), hyphens (-), and Chinese characters.

4. On the displayed page, confirm the instance details.
   • If you need to modify the settings, 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 creation is complete, the status changes to Available.

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

   • During creation, an automated backup policy is enabled by default. 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. In fact, Cassandra 3.11.3 is compatible with HBase and its usage is the same as that of HBase. So, feel free to use it.