Binding or Unbinding an EIP

You can bind an EIP to a TaurusDB instance for public access and unbind it as required.

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 TaurusDB instance.
After an EIP billed on a pay-per-use basis is unbound from a TaurusDB instance, it is still billed. To save money, you can release the EIP or bind it to another DB 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.

Log in to the management console.
Click in the upper left corner and select a region and project.
Click in the upper left corner of the page and choose Databases > TaurusDB.
On the Instances page, click the instance name to go to the Basic Information page.
In the Network Information area, click Bind under Public IP Address (EIP).
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.
In the Network Information area, locate Public IP Address (EIP) and view the bound EIP.

Log in to the management console.
Click in the upper left corner and select a region and project.
Click in the upper left corner of the page and choose Databases > TaurusDB.
On the Instances page, click the DB instance that has an EIP bound.
In the Network Information area on the displayed Basic Information page, click Unbind under Public IP Address (EIP).
In the displayed dialog box, click OK.
In the Network Information area on the Basic Information page, check the result.

You can also see the progress and result of unbinding an EIP from a DB instance on the Task Center page.

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