You can switch the network type of an ApsaraDB for Redis instance from classic network
to virtual private cloud (VPC). Then, clients in the same VPC can communicate with
the ApsaraDB for Redis instance at higher security levels and lower network latency.
The instance runs in the classic network.
Note You can view the network type in the Basic information section of the instance.
- After you switch the network type of an instance from classic network to VPC, you
cannot switch back to classic network.
- The instance may experience a transient connection of a few seconds. We recommend
that you perform this operation during off-peak hours and make sure that your applications
can automatically reconnect to the instance.
- When you switch the network type, you can specify whether to retain the classic network
endpoint of the instance. If you do not retain the classic network endpoint, the endpoint
is released after the network type is switched. Then, clients cannot connect to the
instance by using the classic network endpoint. In this case, you must change the
database endpoint on your client at the earliest opportunity.
Network types of ApsaraDB for Redis instances
||A VPC is a private network dedicated to your Alibaba Cloud account. VPCs are logically
isolated from each other at Layer 2 to provide higher security and performance. If
a client is deployed on an Elastic Compute Service (ECS) instance, you can connect
the client to an ApsaraDB for Redis instance over a VPC for higher security and lower
network latency. For more information about ECS instances, see What is ECS?
||Cloud services on the classic network are not isolated. Unauthorized access can be
blocked only by using security groups or whitelists.
Note If a client is deployed in a VPC and an ApsaraDB for Redis instance is deployed in
the classic network, the client cannot connect to the instance. To connect the client
to the instance, switch the network of the instance to the client VPC.
- Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance is deployed.
Then, find the instance and click the instance ID.
- On the right side of the Connection Information section, click Switch to VPC.
- In the panel that appears on the right side of the page, set the parameters.
||Select the VPC and vSwitch that you want to use.
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 Work with vSwitches
|Retain the connection address of the classic network
||Specify whether to retain the classic network endpoint of the ApsaraDB for Redis instance:
- Yes: allows the instance to use both the classic network and VPC endpoints within a specified
period of time. Clients can connect to the instance by using both endpoints. However,
you must change the database endpoint on your client to the VPC endpoint before the
classic network endpoint becomes invalid.
- No: releases the classic network endpoint. Clients cannot connect to the instance by
using the classic network endpoint.
||Specify the retention period of the classic network endpoint. Unit: day. You can also
modify the retention period after you switch the network type. For more information,
see Modify the expiration date of a classic network endpoint.
- Click OK.
Related API operations
||Switches the network type of an ApsaraDB for Redis instance from classic network to