Binding an EIP

Scenarios

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

Precautions

• Binding EIPs to DB instances reduces the security of the DB instances. Exercise caution when performing this operation. 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 the GaussDB(for MySQL) instance.
• Traffic generated by the public network is billed. You can unbind the EIP from your DB instance when the EIP is no longer used.
• After an EIP billed on a pay-per-use basis is unbound from a GaussDB(for MySQL) instance, it is still billed. To save money, you can release the EIP or bind it to another DB instance.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > GaussDB(for MySQL).
4. On the Instances page, click the instance name to go to the Basic Information page.
5. In the Network Information area, click Bind in the Public IP Address (EIP) field.
6. In the displayed dialog box, select an EIP and click OK.
   If no EIPs are available, click View EIP to create an EIP on the network console. After the EIP is created, go back to the Basic Information page and bind the newly created EIP to the instance.

   

   You need to configure security group rules and enable specific IP addresses and ports to access the DB instance.

   Figure 1 Selecting an EIP
   

7. In the Public IP Address (EIP) field of the Network Information area, view the EIP that was bound.