Help Center/ GeminiDB/ GeminiDB Influx API/ Working with GeminiDB Influx API/ Instance Connection and Management/ Connection Information Management/ Binding an EIP to or Unbinding an EIP from a GeminiDB Influx Instance Node
Updated on 2026-05-08 GMT+08:00
View PDF
Share

Binding an EIP to or Unbinding an EIP from a GeminiDB Influx Instance Node

Scenarios

By default, GeminiDB Influx instances are accessible only over a private network to help ensure data security and access efficiency. To access a GeminiDB Influx instance from outside the private network, you can bind an EIP to a node in the instance so it can be reached over a public network.

Binding an EIP directly to an instance node increases security risks. If security rules are misconfigured or a vulnerability is exploited, an attacker may obtain your access credentials and perform malicious operations on database resources. You are advised to obtain an EIP by binding a public gateway address instead.

This section describes how to bind an EIP to or unbind an EIP from a GeminiDB Influx instance node.

Usage Notes

  • Your instance must have a load balancer address. If no load balancer address is available, you can submit a service ticket on the console to contact the customer service.
  • If an EIP has been bound to an instance node, you must unbind it before binding a public gateway address.
  • You need to estimate required bandwidth and buy an EIP with sufficient bandwidth resources. Client access exceptions caused by poor public network performance will not be included in the SLA.
  • You need to set security groups and enable IP addresses and ports to access the instance. Before accessing a database, you need to request an EIP on the VPC console and add the IP address or CIDR block of the database to an inbound rule. For details, see Setting a Security Group Rule.
  • Public access reduces instance security. To achieve a higher transmission rate and security level, you are advised to migrate your applications to the ECS that is in the same region as your GeminiDB Influx instance.
  • After the public gateway is unbound from a GeminiDB Influx instance, the associated EIP is retained. If the EIP is billed on a pay-per-use basis, it will continue to incur charges. To avoid extra charges, release the EIP manually if it is no longer needed.

Billing

For details about EIP pricing, see EIP Pricing Details.

Procedure

  1. Log in to the GeminiDB console.
  2. On the Instances page, click the target instance name.
  3. In the Node Information area of the displayed Basic Information page, locate the target node and click Bind EIP in the Operation column.

    Figure 1 Binding an EIP

  4. In the displayed dialog box, select an EIP and click OK. If no available EIPs are displayed, click View EIP and create an EIP on the VPC console.

    Figure 2 Selecting an EIP

  5. In the EIP column of the node, check that the EIP is successfully bound.

    To unbind the EIP, see Unbinding an EIP.

  1. Log in to the GeminiDB console.
  2. On the Instances page, click the name of the instance whose node has an EIP bound to it to go to the Basic Information page.
  3. In the Node Information area of the displayed Basic Information page, locate the target node and click Unbind EIP in the Operation column.

    Figure 3 Unbinding an EIP

  4. In the displayed dialog box, click Yes.

Helpful Links

Binding or Unbinding a Public Gateway Address

Related APIs

API

Description

Binding/Unbinding an EIP

Binds an EIP to or unbinds an EIP from an instance node.
Parent Topic: Connection Information Management