Buying a Cluster Instance

Prerequisites

• You have created a Huawei Cloud account.

Procedure

1. Log in to the GeminiDB console.
2. In the service list, choose Databases > GeminiDB Redis API.
3. On the Instances page, click Buy DB Instance.
4. On the displayed page, specify a billing mode and 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 In this mode, specify Required Duration at the bottom of the page. The system bills you 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 Yearly/Monthly 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 How Do I Unsubscribe from Yearly/Monthly Instances?. Pay-per-use If you select this billing mode, you are billed based on how much time the instance is in use. If you expect to use an instance for a long period of time, change its billing mode to yearly/monthly to optimize costs. For details, see Pay-per-Use to Yearly/Monthly.

   Table 2 Basic information

   Parameter	Description
   Region	Region where a tenant is located NOTICE: Select a region near to your service area to reduce network latency and experience faster access. 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. Contains 4 to 64 characters and must start with a letter. It is case-sensitive and allows only letters, digits, hyphens (-), and underscores (_). If the name contains Chinese characters, the length cannot exceed 64 bytes. You can change the name of an instance after it is created. For details, see Modifying the Name of an Instance.
   Compatible API	Redis.
   Product Type	Standard: Stable and low-latency performance is provided, suitable for common scenarios such as advertising and recommendation, gaming, e-commerce, and Internet of Vehicles (IoV). Capacity-oriented: Large-capacity key-value storage is provided, suitable for average performance requirements and expectations of low costs.
   DB Instance Type	Cluster: With a sharded cluster architecture, a cluster instance can be connected through proxies and is compatible with a single Redis node, Redis Sentinel, and Redis Cluster. The cluster instance has strong horizontal scaling capabilities and can handle millions of QPS and dozens of TB of data.
   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. 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 nodes of your instance will be evenly distributed across the three AZs.

   Figure 2 Storage and specifications (standard)
   
   Figure 3 Storage and specifications (cloud native)
   

   Table 3 Specifications and storage

   Parameter	Description
   Instance Creation Method	Two options are available: Fast configure Provides you with recommended specifications. You can select one of them based on service requirements, without the need to specify the 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 Provides a standard process to configure instance specifications, including specifying the specifications, node quantity, and storage space. Currently, a maximum of 36 nodes are supported. To obtain more nodes, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact customer service.
   Instance Specifications	Higher CPU specifications provide better performance. Select specifications based on your service requirements. 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.
   Autoscaling	You can determine whether to enable the function based on the site requirements. Storage Usage: If the storage usage exceeds the value you set, the system automatically scales up your instance storage. The options are 60%, 65%, 70%, 75%, 80%, 85%, and 90%. Increase by: specifies the ratio of the increased storage space each time to the total storage space. The value can be 10%, 15%, or 20%.
   Static Data Encryption	You can determine whether to encrypt static data. Disable: Data is not encrypted. Enable: If you select this option, 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 plaintext 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. NOTE: This function is in the open beta test (OBT) phase. To use this function, contact customer service. An agency will be created after static data encryption is enabled. After an instance is created, the static data 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.

   Table 4 Network

   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 one. 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 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. If you want to connect to a GeminiDB Redis instance through an ECS over an internal network, the GeminiDB Redis instance and the ECS must be in the same VPC. If they are not in the same VPC, you can create a VPC peering connection to enable access.
   Subnet	A subnet where your instance is created. The subnet provides dedicated and isolated networks, improving network security. NOTE: Create an IPv4 subnet or select an existing one. IPv6 subnets are not supported.
   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.
   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: 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. NOTE: You cannot change the database port after an instance is created.

   Table 5 Database configuration

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

   Table 6 Password-free access configuration

   Parameter

   Description

   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 Tags

   Parameter

   Description

   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. If your organization has configured a tag policy for your GeminiDB Redis instance, 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 is unique for each instance. It 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 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 Managing Tags.

   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 parameter, the auto-renew cycle is determined by the selected required duration.

5. On the displayed page, confirm instance details.
   • For yearly/monthly instances
     • 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.

6. 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.