You can change the virtual private cloud (VPC) or vSwitch of a Tair instance to the VPC of an Elastic Compute Service (ECS) instance so that you can connect the ECS instance and the Tair instance over an internal network.

Prerequisites

  • The instance does not have a private endpoint. If the direct connection mode is enabled for the instance, you can release the private endpoint, change the VPC of the instance, and then re-enable the direct connection mode. For more information about private endpoints and the direct connection mode, see Enable the direct connection mode.
  • The password-free access feature is disabled for the instance. No Data Transmission Service (DTS) data migration tasks or synchronization tasks that involve the instance are running. Otherwise, an error is reported. For more information about password-free access and DTS, see Enable password-free access and What is DTS?

Scenarios

OperationScenario
Change the VPC of an instanceClients are unable to communicate with your Tair instance because the clients and the instance belong to different VPCs.

For example, the ECS instance on which your workloads are running is deployed in VPC A and the Tair instance is deployed in VPC B. To connect the Tair instance to the ECS instance, you can change the VPC of the instance to VPC A.

Change the vSwitch of an instanceTo manage cloud resources and IP address whitelists in a centralized manner, you can group the cloud resources based on workloads and then allocate IP addresses.

For example, you can connect cloud resources that are related to database services, such as ECS instances and Tair instances, to the same vSwitch. Then, these cloud resources are assigned IP addresses that belong to the same CIDR block.

Impacts

  • If you change the VPC or vSwitch of an instance, the instance encounters transient connections for 30 seconds. Make sure that you change the VPC or vSwitch during off-peak hours and your applications can automatically reconnect to the instance.
  • If you change the VPC or vSwitch of an instance, the virtual IP address (VIP) of the instance is changed. If your applications are connected to the VIP of the instance, the connections are closed after the VIP is changed.
    Note After you change the VPC or vSwitch of an instance, the endpoint of the instance, such as r-hp3bpn39cs1vu****.redis.hangzhou.rds.aliyuncs.com, remains unchanged. We recommend that you connect your applications to instances by using endpoints.
  • A VIP change interrupts Data Management (DMS) for a short period of time. For more information about DMS, see Overview. After the VIP is changed, the connections are resumed.
  • After you change the VPC or vSwitch of an instance, clear the cache on clients. Otherwise, clients may be unable to write data to the instance and can only read data from the instance.

Procedure

  1. Log on to the Tair console and go to the Instances page. In the top navigation bar, select the region in which the instance that you want to manage resides. Then, find the instance and click its ID.
  2. In the Basic Information section, click Modify next to the VPC ID.
    Note If you want to change only the vSwitch, you can click Modify next to the vSwitch ID.
  3. In the panel that appears, select the VPC and the vSwitch that you want to use.
    Note If no VPC or vSwitch is available in the drop-down list, create a VPC and a vSwitch. The vSwitch and the instance must belong to the same zone. For more information, see Create and manage a VPC and Create and manage a vSwitch.
  4. Click OK.
    Warning If you change the VPC or vSwitch of an instance, the instance encounters transient connections for 30 seconds. Make sure that you change the VPC or vSwitch during off-peak hours and your applications can automatically reconnect to the instance.
  5. In the message that appears, read the content and click OK.

Related API operations

OperationDescription
SwitchNetworkChanges the VPC or vSwitch of a Tair instance. If the Tair instance is deployed in the classic network, the network type of the instance changes from classic network to VPC.