Change the virtual private cloud (VPC) and vSwitch of an AnalyticDB for MySQL cluster when the cluster and an Elastic Compute Service (ECS) instance are in different VPCs and you need them to communicate over an internal network.
Before you begin
Ensure that a target VPC and vSwitch exist in the same region as the cluster. If not, create a VPC and vSwitch first.
Impacts and considerations
Changing the VPC and vSwitch is an asynchronous operation. Review the following impacts before you proceed.
During the change:
The cluster may experience brief connection drops and read/write failures. Perform this operation during off-peak hours and make sure your application is configured to automatically reconnect.
The cluster status changes to Modifying Network Address and returns to Running when the change is complete.
After the change:
Virtual IP address (VIP) change: The VIP of the cluster may change. Use the cluster's VPC endpoint instead — it remains the same after the change. Example:
am-bp13er819d288****90650.ads.aliyuncs.com.DNS cache: The DNS cache on your machine refreshes after the change completes, which may cause connection failures for several minutes.
Resources not automatically updated after the change:
| Resource | Action required |
|---|---|
| IP address whitelists | If the cluster's CIDR block changes, existing whitelists may become invalid. Reconfigure them. |
| Elastic Network Interface (ENI) | If the ENI feature is enabled, the ENI is not switched to the new VPC or vSwitch. Disable the ENI feature and then re-enable it. |
| Notebook resources (Enterprise, Basic, and Data Lakehouse editions only) | Update the VPC ID and vSwitch ID parameters of notebook resources to the new VPC and vSwitch. Otherwise, job submissions fail. |
Deleting the original VPC and vSwitch:
Enterprise Edition, Basic Edition, Data Lakehouse Edition, and Data Warehouse Edition (elastic mode): You can delete the original VPC and vSwitch after the change.
Data Warehouse Edition (reserved mode): You cannot delete the original VPC and vSwitch. Specific underlying applications remain deployed there.
Change the VPC and vSwitch
Log on to the AnalyticDB for MySQL console. In the upper-left corner, select a region. In the left-side navigation pane, click Clusters. On the Clusters page, find your cluster and click the cluster ID.
In the Network Information section, click Change VPC and vSwitch to the right of the VPC ID.
In the Change VPC and vSwitch dialog box, select a VPC and a vSwitch.
If no options appear, the region has no other VPCs or vSwitches. Create a VPC before proceeding.
Click OK. The cluster status changes to Modifying Network Address. When the status returns to Running, the change is complete.
相关API
API接口 | 说明 |
ModifyDBClusterVip - 切换专有网络和交换机 | 切换数仓版集群的专有网络VPC或交换机。 |
What to do next
If the VIP changed, update your application's connection string. Use the VPC endpoint to avoid future disruptions.
If the cluster's CIDR block changed, review and reconfigure IP address whitelists.
If ENI was enabled, disable and re-enable it to apply the new network settings.
For Enterprise, Basic, or Data Lakehouse edition clusters, update the VPC ID and vSwitch ID in your notebook resources.