doc-exports/docs/geminidb/umn/nosql_02_0008.html

Binding an EIP

Scenarios

The Elastic IP service provides independent public IP addresses and bandwidth for Internet access. After you create a GeminiDB Cassandra 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

• Before accessing a database, you need to 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 section Configuring Security Group Rules.
• To change the EIP that has been bound to a node, you need to unbind it from the node first.

Binding an EIP

1. On the Instance Management page, click the target GeminiDB Cassandra instance.
2. On the Basic Information page, in the Node Information area, locate the target node and click Bind EIP in the Operation column.
3. In the displayed dialog box, all available unbound EIPs are listed. Select the required EIP and click OK. If no available EIPs are displayed, click View EIP and create an EIP on the VPC console.
4. 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. On the Instance Management page, click the target GeminiDB Cassandra instance.
2. On the Basic Information page, in the Node Information area, locate the target node and click Unbind EIP in the Operation column.
3. In the displayed dialog box, click Yes.

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

Parent topic: Connecting to a GeminiDB Cassandra Instance Over Public Networks