Buying a GeminiDB HBase Instance

Prerequisites

• You have signed up for a HUAWEI ID and completed real-name authentication.

  Before buying a GeminiDB HBase instance, sign up for a HUAWEI ID and enable Huawei Cloud services.

  If you have enabled Huawei Cloud services, skip this step.

• You can create an IAM user or user group on the Identity and Access Management (IAM) console and grant it specific operation permissions for fine-grained permissions management. For details, see Creating a User and Granting Permissions.

Procedure

1. Log in to the GeminiDB console.
2. On the Instances page, click Buy DB Instance.
3. On the displayed page, select a billing mode, set Compatible API to HBase, set other parameters, and click Next. If HBase is unavailable, contact the customer service.
   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. 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 from a Yearly/Monthly Instance. Pay-per-use You do not need to set Validity Period because you are billed based on how long you have actually used your instance. 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, deploy your DB 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 GeminiDB is compatible with mainstream NoSQL databases, including Redis, DynamoDB, Cassandra, HBase, MongoDB, and InfluxDB. You can select GeminiDB APIs by following How Do I Select an API?
   Deployment 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.
   DB Instance Type	Cluster One cluster consists of at least three nodes. A cluster can be easily scaled out to meet increasing data growth needs. It is recommended when high availability, large data volumes, and seamless scalability are required.
   AZ	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 3 Specifications and storage
   

   Table 3 Specifications and storage

   Parameter	Description
   Instance Specifications	Higher CPU specifications provide better performance. Select specifications as needed.
   Nodes	Number of nodes that the instance is deployed on. If the number of nodes exceeds the upper limit, you can choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service. After an instance is created, you can add nodes. For details, see Manually Adding Instance Nodes.
   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.
   Auto Scale	Whether autoscaling is enabled. You can enable Auto Scale after an instance is created. For details, see Configuring Storage Autoscaling for an Instance.
   Disk Encryption	You can select to enable disk encryption based on service requirements. 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 writes and reads. Key Name: Select an existing key or create one. To use a shared key, ensure that you have created an agency. For details, see Creating an Agency (by a Delegating Party). Select another account from the drop-down list to share the key of the current account. VPC owners can share the keys with one or multiple accounts through Resource Access Manager (RAM). For details, see Creating a Resource Share. Enter a key ID. The key must be in the current region. NOTE: This function is now in CBT. To use it, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service. After an instance is created, the disk encryption status and the key cannot be changed. The key cannot be disabled, deleted, or frozen when being used. Otherwise, the database becomes unavailable. For details about how to create a key, see Creating a Key in Data Encryption Workshop User Guide.

   Figure 4 Network configuration
   

   Table 4 Network configuration

   Parameter	Description
   VPC	A dedicated virtual network where your instance is located. It isolates networks for different workloads to enhance security. The system will assign a default VPC (default_vpc). You can also use an existing, new, or shared VPC. After an instance is created, the VPC cannot be changed. Select an existing VPC of the current account from the drop-down list. To use a new VPC, create a VPC first and then select it from the drop-down list. For details about how to create a VPC, see Creating a VPC with a Subnet in Virtual Private Cloud User Guide. Select a VPC shared by another account from the drop-down list. VPC owners can share the subnets in a VPC with one or multiple accounts through Resource Access Manager (RAM), which ensures cost efficiency of network resources. For more information about VPC subnet sharing, see VPC Sharing in Virtual Private Cloud User Guide. NOTE: To connect an instance to an ECS over a private network, ensure they are in the same VPC. If they are not, 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 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 automatically allocates resources to you.

   Figure 5 Database configuration
   

   Table 5 Database configuration

   Parameter	Description
   Administrator	Username of the administrator account. The default value is rwuser.
   Administrator Password	Password of the administrator account. The password: Can include 8 to 32 characters. 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	This password must be consistent with administrator password.
   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.
   Parameter Template	A parameter template contains the configuration values of a database engine. The parameters can be applied to one or more instances of the same type. After creating an instance, you can modify the parameter template. You can modify the instance parameters as required after the instance is created.
   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 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 How Can I Connect to a GeminiDB HBase Instance over TLS (SSL)?

   Table 6 Tags

   Parameter

   Description

   Tags

   (Optional) Identifier of a GeminiDB HBase instance. Adding tags helps you better identify and manage your instance. A maximum of 20 tags can be added for each instance. If your organization has configured a tag policy, 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 will 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 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: _.-:+=@/

4. On the displayed page, confirm 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 the created instance.
   • The instance status is displayed as Creating.
   • After the instance is created, its status becomes Available.

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

   • An automated backup policy is enabled by default during instance creation. After the instance is created, a full backup is created.