Binding and Unbinding an EIP

Scenarios

An EIP provides independent public IP addresses and bandwidth for Internet access. After you create a GeminiDB Influx instance, you can bind an EIP to it to allow external access. If later you want to prohibit external access, you can also unbind the EIP from the DB instance.

Precautions

• This function is in the open beta test (OBT) phase. To use the function, contact customer service.
• Configure security group rules and enable specific IP addresses and ports to access the target DB instance. Before accessing a database, apply for an EIP on the VPC console. Then, add an inbound rule to allow the IP addresses or IP address ranges of ECSs. For details, see Configuring Security Group Rules.
• To change the EIP that has been bound to a node, unbind it from the node first.

Binding an EIP

1. Log in to the management console.
2. In the service list, choose Databases > GeminiDB.
3. On the Instances page, locate the instance to which you want to bind an EIP to and click its name.
4. On the Basic Information page, in the Node Information area, locate the target node and click Bind EIP in the Operation column.
   Figure 1 Binding an EIP
   

5. In the displayed dialog box, all available unbound EIPs are listed. Select the required EIP and click Yes. If no available EIPs are displayed, click View EIP and create an EIP on the VPC console.
   Figure 2 Selecting an EIP
   

6. In the EIP column, view the EIP that is successfully bound.

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

Unbinding an EIP

1. Log in to the management console.
2. In the service list, choose Databases > GeminiDB.
3. On the Instance Management page, click the instance that you want to unbind an EIP from.
4. On the Basic Information page, in the Node Information area, locate the target node and click Unbind EIP in the Operation column.
   Figure 3 Unbinding an EIP
   

5. In the displayed dialog box, click Yes.

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