Buying and Connecting to a Cluster Instance

This section describes how to buy a GeminiDB Influx cluster instance on the GeminiDB console and connect to the instance.

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 if you have high requirements on availability, large volume of data, and future scalability.

Each tenant has up to 50 GeminiDB Influx instances by default. To request a higher quota, contact customer service.

• Step 1: Buying a Cluster Instance
• Step 2: Connecting to an Instance Through DAS

  For details about other connection methods, see Connection Methods.

1. Log in to the GeminiDB console.
2. In the service list, choose Databases > GeminiDB Influx API.
3. On the Instances page, click Buy DB Instance.
4. On the displayed page, select a billing mode, configure instance specifications, and click Next.

   The following parameters are for reference only. Select proper specifications as needed. Table 1 lists details about the parameters.

   Figure 1 Billing mode and basic information
   

   Parameter	Example Value	Description
   Billing description	Pay-per-use	Billing mode of an instance Yearly/Monthly: A prepaid billing mode in which you pay for resources before using it. Bills are settled based on the subscription period. The longer the subscription term, the bigger the discount. This mode is a good option for long-term stable services. Pay-per-use: A postpaid billing mode. Pay as you go and just pay for what you use. The DB instance usage is calculated by the second but billed every hour. 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	Select CN-Hong Kong.	The region where the tenant is located. It can be changed in the upper left corner. NOTICE: Select the nearest region where you will access the instance from, so latency can be kept to a minimum and response will be faster. 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	User-defined	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.
   Compatible API	InfluxDB	-
   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 if you have high requirements on availability, large volume of data, and future scalability.
   Compatible Version	1.8	1.8
   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. An instance can be deployed in one or three AZs. If you want to deploy an instance in a single AZ, select one AZ. If you want to deploy your instance across AZs for disaster recovery, select three AZs. Nodes of the instance are evenly distributed across the three AZs.

   Figure 2 Storage and specifications
   

   Parameter	Example Value	Description
   Data Node Specifications	2U8GB	Data nodes provide read and write capabilities for time series databases. The specifications depend on configurations of the DFV shared resource pool and memory. Select specifications based on service requirements. For details about supported specifications, see Instance Specifications.
   Data Nodes	3	Select the number of data nodes based on service requirements. After an instance is created, you can add nodes. For details, see Adding Nodes.
   Storage Space	100GB	The storage is an integer and the minimum storage is 100 GB. You can add a minimum of 1 GB at a time.
   Purchase Cold Storage	No	Do not purchase cold storage. If you do not enable cold storage when creating an instance, you can enable it later based on service requirements. For details, see Enabling Cold Storage. NOTE: Cold storage cannot be disabled after being enabled.

   Figure 3 Network and database configurations
   

   Parameter	Example Value	Description
   VPC	default_vpc	Virtual private network where your DB instances are located. A VPC isolates networks for different services. You can select an existing VPC or create a VPC. NOTE: After a GeminiDB Influx instance is created, the VPC where the instance is deployed cannot be changed. If you want to connect to a GeminiDB Influx instance from 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.
   Subnet	default_subnet	A subnet provides dedicated network resources that are logically isolated from other networks for security purposes.
   Security Group	default	A security group controls access between GeminiDB Influx 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.
   Administrator Password	Configured based on the password policy	Password of the administrator account. The password: Can contain 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.
   Parameter Template	Default-InfluxDB-1.8	A template of parameters for creating an instance. The template contains API configuration values that are applied to one or more instances. After an instance is created, you can modify its parameters to better meet your service requirements. For details, see Modifying Parameters of GeminiDB Influx Instances.
   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.

   Retain the default values for other parameters.

5. On the order confirmation page, check the instance information. If you need to modify the information, click Previous. If no modification is required, read and agree to the service agreement and click Submit.
6. Click Back to Instance Management to go to the instance list.
7. On the Instances page, view and manage the created instance.
   • Creating an instance takes about 5 to 9 minutes. During the process, the instance status displayed in the DB instance list is Creating.
   • After the creation is complete, the instance status changes to Available.
   Figure 4 Successful purchase