Help Center/ GaussDB/ User Guide/ Instance Management/ Binding and Unbinding an EIP for a GaussDB Instance
Updated on 2026-06-01 GMT+08:00
View PDF
Share

Binding and Unbinding an EIP for a GaussDB Instance

Scenarios

You can bind an EIP to a GaussDB instance for public access and can unbind the EIP from an instance as required.

Precautions

  • To ensure that a DB instance is accessible, the security group associated with the instance must allow access to its database port. For example, if the database port is 1611, ensure that the inbound rule of the security group allows access to port 1611. For details about how to configure a security group, see Configuring Security Group Rules for a GaussDB Instance.
  • If a DB instance has already been bound with an EIP, you must unbind the EIP from the instance first before binding a new EIP to it.
  • An EIP can be bound to only one node IP address of a DB instance.
  • Security risks may arise after an EIP is bound to an instance. To enhance database security, set strict inbound and outbound rules for the security group. For details about how to configure a security group, see Configuring Security Group Rules for a GaussDB Instance.

Billing

EIPs must be purchased separately. For details about EIP billing, see EIP Pricing Details.

Procedure

  1. Log in to the GaussDB console.
  2. On the Instances page, click the name of the target instance to go to the Basic Information page.
  3. In the Node List area, click Bind EIP in the Operation column.

    For a distributed instance using independent deployment, switch to CN in the filter area first and then bind an EIP.
    Figure 1 Binding an EIP (for a distributed instance using independent deployment)

    Figure 2 Binding an EIP (for a distributed instance using combined deployment)

    Figure 3 Binding an EIP (centralized instance)

    When using a driver to connect to database in a DB instance, you are advised to bind an EIP to each node that has a private IP address in the instance. When establishing the connection, configure a connection string with multiple IP addresses, for example, jdbc:gaussdb://ip1:port,ip2:port,ip3:port/database. This configuration ensures that if a single node fails, the driver automatically switches to an available node, ensuring the reliability and continuity of database operations. For details about how to use a driver to connect to a database, see Application Development Guide (Distributed) or Application Development Guide (Centralized).

  4. In the displayed dialog box, select the required EIP and click OK.

    If no available EIPs are displayed, click View EIP and obtain an EIP.

    Figure 4 Binding an EIP

  5. In the Node List area, check the operation result in the EIP column.

    Figure 5 Checking the binding result

    To unbind the EIP from the instance, see Unbinding an EIP.

  1. Log in to the GaussDB console.
  2. On the Instances page, click the instance that has been bound with an EIP.
  3. In the Node List area, click Unbind EIP in the Operation column.

    • For a distributed instance, switch to CN in the filter area first and then click Unbind EIP in the Operation column.
    • For a centralized instance, click More and choose Unbind EIP in the Operation column.
    Figure 6 Unbinding an EIP (distributed instance)

    Figure 7 Unbinding an EIP (centralized instance)

  4. In the displayed dialog box, click OK to unbind the EIP.
  5. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

    Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

  6. In the Node List area, check the operation result in the EIP column.

    To bind an EIP to the instance again, see Binding an EIP.

Parent Topic: Instance Management