Buying and Connecting to a GeminiDB DynamoDB-Compatible Instance

1. Log in to the GeminiDB console.
2. On the Instances page, click Buy DB Instance.
3. Set Billing Mode and Region.
   Figure 1 Basic settings
   

   Table 1 Basic settings

   Parameter	Example Value	Description
   Billing Mode	Pay-per-use	Billing mode of an instance Yearly/Monthly: You prepay for an instance based on the required duration. Longer subscriptions offer larger discounts. This mode is a good option for long-term stable workloads. Pay-per-use: You are billed based on how long you have actually used GeminiDB. Pricing is listed on a per-hour basis, and bills are calculated down to the second. This mode allows you to adjust resource usage easily. You neither need to prepare for resources in advance, nor end up with excessive or insufficient preset resources.
   Region	CN-Hong Kong	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.

4. Set Compatible API to DynamoDB.
5. Set Deployment Type and DB Instance Type.
   Figure 2 Resource configuration
   

   Table 2 Resource configuration

   Parameter	Example Value	Description
   Deployment Type	Cloud native	Select Classic or Cloud native. Classic: classic architecture with decoupled storage and compute Cloud native: new, more flexible, new-gen version with support for more AZs
   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	AZ 1, AZ 2, and AZ 3	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. To deploy instances in a single AZ, select one AZ. If you want to deploy an instance across AZs for disaster recovery, select three AZs. In this deployment mode, the nodes are evenly distributed across the three AZs.

6. Set specifications and storage.
   Figure 3 Specifications and storage
   

   Parameter	Example Value	Description
   Instance Specifications	2 vCPUs | 8 GB	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 of a GeminiDB DynamoDB-Compatible Instance.
   Nodes	3	Number of nodes that the instance is deployed on. If the number of nodes exceeds the upper limit, you can submit a service ticket on the console to contact the customer service. After an instance is created, you can add nodes. For details, see Manually Adding Nodes to a GeminiDB DynamoDB-Compatible Instance.
   Storage Space	500 GB	Instance storage space. The range depends on the instance specifications. For details, see Instance Specifications. After an instance is created, you can scale up its storage if necessary. For details, see Manually Scaling Up Storage of a GeminiDB DynamoDB-Compatible Instance.
   Auto Scale	Toggled off	Specifies whether to enable autoscaling. This function is only available to instances with classic storage. You can also enable Auto Scale after an instance is created. For details, see Configuring Storage Autoscaling for a GeminiDB DynamoDB-Compatible Instance.
   Disk Encryption	Disable	Specifies whether to enable disk encryption. If you select 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.

7. Set a password.
   Figure 4 Setting a password
   

   Table 3 Setting a password

   Parameter	Example Value	Description
   Administrator Password	Configured based on the password policy	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.

8. Set Enterprise Project.
   Figure 5 Enterprise project
   

   Table 4 Enterprise project

   Parameter	Example Value	Description
   Enterprise Project	default	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.

9. Retain the default values for other parameters and click Buy Now.
10. On the displayed page, confirm instance details. To modify the configurations, click Previous.
11. If no modification is required, read and agree to the service agreement and click Submit.
12. Click Back to Instance Management to go to the instance list.
13. 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.
    Figure 6 Available instance
    

This section describes how to connect to a GeminiDB DynamoDB-Compatible instance using Java.

Prerequisites

• A GeminiDB DynamoDB-Compatible instance has been created.
• An ECS has been created. For details about how to create an ECS, see Purchasing an ECS in the Elastic Cloud Server documentation.
• JDK has been installed on the ECS.

Obtaining the Connection Address of a GeminiDB DynamoDB-Compatible Instance

1. Log in to the Huawei Cloud console.
2. On the Instances page, click the target instance name. On the displayed Basic Information page, view the load balancer address.
   

   If no load balancer address is available, submit a service ticket on the console to contact the customer service.

   Figure 7 Viewing the IP address
   

Connecting to an Instance

public class ClientExample{  
    public static AWSCredentialsProvider myCredentials = new AWSStaticCredentialsProvider(new BasicAWSCredentials("rwuser", "your_pwd"));  
    public static void main(String[] args) {  
        AmazonDynamoDB client = AmazonDynamoDBClientBuilder.standard()  
            .withEndpointConfiguration(new AwsClientBuilder.EndpointConfiguration("http://ip", "cn-north-1"))
            .withCredentials(myCredentials)  
            .build();  
        DynamoDB dynamoDB = new DynamoDB(client);  
        TableCollection res = dynamoDB.listTables();  
        System.out.println(res);  
    }  
}