Updated on 2025-04-01 GMT+08:00

Buying a GeminiDB Influx Cluster Instance

This section describes how to buy a cluster instance that is compatible with InfluxDB APIs on the GeminiDB console.

Each tenant can create a maximum of 50 GeminiDB Influx instances by default. To request a higher quota, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact customer service.

Prerequisites

  • You have created a Huawei Cloud account.

Procedure

  1. Log in to the Huawei Cloud console.
  2. In the service list, choose Databases > GeminiDB.
  3. On the Instances page, click Buy DB Instance.
  4. On the displayed page, specify instance specifications and click Next.

    Figure 1 Billing mode and basic information
    Table 1 Billing description

    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
      • If you select this billing mode, you are billed based on how much time the instance is in use.
      • 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

    The region where the tenant is located. It can be changed in the upper left corner.

    NOTICE:

    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 (_). 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 Changing a GeminiDB Influx Instance Name.

    Compatible API

    InfluxDB

    DB Instance Type

    Cluster

    One cluster consists of at least three nodes. Nodes can be added to a cluster, which is unsuitable to cope with the ever growing data volume.

    DB Engine Version

    • 1.8
    • 1.7

    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

    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.

    Nodes

    Select the number of nodes based on service requirements. After an instance is created, you can add nodes. For details, see Adding Instance Nodes.

    Currently, a maximum of 12 nodes are supported. To create more nodes, choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact customer service.

    Storage Space

    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

    Cold storage is used to store historical data that is not frequently queried. When purchasing a GeminiDB Influx instance, you can purchase cold storage and configure the retention policy to specify the retention period of hot data. In this way, hot data will be automatically archived in cold storage after the retention period expires, reducing storage costs. The value can be:

    • Yes

      Set the cold storage capacity to suit your service requirements.

    • No

      Do not purchase cold storage.

    For more information about cold and hot data separation, see Cold and Hot Data Separation.

    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.

    Cold Storage

    The cold storage is an integer from 500 GB to 100,000 GB. You can add a minimum of 1 GB each time you scale up storage space.

    After an instance is created, you can scale up its cold storage. For details, see Scaling Up Cold Storage.

    Figure 3 Network and database configurations
    Table 4 Network configurations

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

    If there are no VPCs available, the system automatically allocates a VPC to you.

    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 using an ECS over a private network, the GeminiDB Influx instance and the ECS must be in the same VPC. If they are not, you can 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 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.

    Table 5 Database configurations

    Parameter

    Description

    Administrator

    Username of the administrator account. The default value is rwuser.

    Administrator Password

    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.

    Confirm Password

    This password must be consistent with the administrator password.

    Parameter Template

    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

    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.

    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.

    After SSL is enabled, you can select the default certificate or the certificate issued by the CCM service.

    NOTE:
    Table 6 Tags

    Parameter

    Description

    Tags

    The setting is optional. Adding tags helps you better identify and manage your instances. 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 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 (-).

    • A tag value is optional if the instance is going to 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 Managing Tags.

    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 renew cycle is the same as the selected duration.

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

  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.

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

    • Automated backup is enabled by default during instance creation. A full backup is automatically triggered after an instance is created.
    • The default database port of the instance is 8635 and cannot be changed.
      Figure 4 Available instance