All Products
Search
Document Center

ApsaraDB for Redis:Switch the network type from classic network to VPC

Last Updated:Feb 19, 2024

ApsaraDB for Redis allows you to switch the network type of an instance from classic network to Virtual Private Cloud (VPC). This way, clients in the same VPC as the instance can communicate with the instance at higher security levels and lower network latency.

Prerequisites

The network type of the instance is classic network.

Note

You can view the network type in the Basic information section of the instance details page.

Impacts

  • After you switch the network type of an instance from classic network to VPC, you cannot switch it 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

Network type

Description

VPC (recommended)

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?

Classic network

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 VPC of the client.

Procedure

  1. 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 its ID.
  2. On the right side of the Connection Information section, click Switch to VPC.

  3. In the panel that appears, configure the parameters.

    切换为专有网络

    Parameter

    Description

    VPC Network

    Select the VPC and vSwitch that you want to use.

    Note

    If no VPC or vSwitch is displayed in the drop-down list, no VPC or vSwitch is available in the region or zone where the ApsaraDB for Redis instance resides. In this case, create a VPC and a vSwitch first. Make sure that the VPC resides in the same region as the ApsaraDB for Redis instance and the vSwitch resides in the same zone as the ApsaraDB for Redis instance. For more information, see Create and manage a VPC and Create and manage a vSwitch.

    VSwitch

    Retain the connection address of the classic network

    Specify whether to retain the classic network endpoint of the ApsaraDB for Redis instance. Valid values:

    • 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.

    Retention Days

    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.

  4. Click OK.

FAQ

Why am I unable to select a vSwitch when I switch the network type of an ApsaraDB for Redis instance?

If no VPC or vSwitch is displayed in the drop-down list, no VPC or vSwitch is available in the region or zone where the ApsaraDB for Redis instance resides. In this case, create a VPC and a vSwitch first. Make sure that the VPC resides in the same region as the ApsaraDB for Redis instance and the vSwitch resides in the same zone as the ApsaraDB for Redis instance. For more information, see Create and manage a VPC and Create and manage a vSwitch.

Can I connect an application to an ApsaraDB for Redis instance that resides in a different zone of the same region?

If the application is deployed on an ECS instance that belongs to the same VPC in the same region as the ApsaraDB for Redis instance, network connectivity is not affected even if the instances are located in different zones. For more information about regions and zones, see Regions and Zones.

Can I keep the endpoint unchanged when I switch the network type of an ApsaraDB for Redis instance from classic network to VPC?

When you switch the network type to VPC, you can choose to retain the classic network endpoint and select the retention period. Before the end of the retention period, you can extend the retention period multiple times. When the retention period ends, the classic network endpoint is released.

For information about how to change the retention period of a classic network endpoint, see Modify the expiration date of a classic network endpoint.

Related API operations

API operation

Description

SwitchNetwork

Switches the network type of an ApsaraDB for Redis instance from classic network to VPC. If the instance is deployed in the classic network, the network type of the instance is switched from classic network to VPC.