Buying a GeminiDB DynamoDB-Compatible Instance

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 parameters

   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 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 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 Pay-per-Use 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 (_). After an instance is created, you can change its name. For details, see Changing an Instance Name.
   Compatible API	DynamoDB 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?
   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 2 Specifications and storage
   

   Table 3 Specifications and storage

   Parameter	Description
   Instance Specifications	Decoupled storage and compute and software-hardware synergy deliver twice or more the performance of a self-managed database with the same specifications. When you create an instance, select higher specification and specify as few nodes as possible. For example, if you need 8 vCPUs, 32 GB, and 6 nodes for an open-source instance, then for a GeminiDB DynamoDB-Compatible instance with 8 vCPUs and 32 GB of memory, you only need 3 nodes. Select appropriate specifications based on the CPU-memory ratio. After an instance is created, you can change its specifications. For details, see Changing vCPUs and Memory.
   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. For details, see Instance Specifications. When configuring storage space of a GeminiDB DynamoDB-Compatible instance, you are advised to enable autoscaling. Then set trigger conditions and limit of autoscaling. After autoscaling is triggered, the system automatically scales up the storage to ensure that the instance has sufficient storage and keeps available. Take care with the following parameters: Trigger If Available Storage Drops To: storage threshold for triggering autoscaling. When the available storage usage drops to a specified threshold or the available storage drops to 10 GB, autoscaling is triggered. Increase By: percentage of storage to be automatically added. If the calculated increase amount is not a multiple of 10, it will be rounded up to the nearest multiple of 10. At least 100 GB can be added each time. Storage Limit: maximum amount that the system can automatically scale up an instance's storage to. The value must be no less than the current storage of your instance and cannot exceed the maximum storage supported by your instance. After an instance is created, you can scale up its storage if necessary. For details, see Manually Scaling Up Storage Space.
   Auto Scale	Whether autoscaling is enabled. Once Auto Scale is enabled, an agency will be created and fees will be automatically deducted. You can enable Auto Scale after an instance is created. For details, see Automatically Scaling Up Storage Space.

   Figure 3 Network configurations
   

   Table 4 Network configuration

   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 automatically allocates a VPC to you. For details, see "Creating a VPC" in the Virtual Private Cloud User Guide. NOTE: After a GeminiDB DynamoDB-Compatible instance is created, the VPC where the instance is deployed cannot be changed. To connect a GeminiDB DynamoDB-Compatible 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 GeminiDB DynamoDB-Compatible API 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.

   Figure 4 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. Can include 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	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.

   Figure 5 Tag configuration
   

   Table 6 Tags

   Parameter

   Description

   Tags

   (Optional) You can tag your GeminiDB DynamoDB-Compatible instances to identify and manage their resources. 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 include up to 36 characters, including digits, letters, underscores (_), and hyphens (-). A tag value is optional if the instance will be tagged. The value can be empty. 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 Tag Management.

   Figure 6 Required duration configuration
   

   Table 7 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	This option is not selected by default. 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.
   • It takes about 5 to 9 minutes to create an instance. During the process, the instance status is 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.
   Figure 7 Instance successfully purchased