Switching a DCS Instance's Subnet

To scale a DCS instance, subnet IP addresses may be insufficient. In this case, switch the subnet. This document describes how to switch an instance's subnet.

Currently in restricted use and disabled by default. To use this function, submit a ticket and contact customer service.

Notes and Constraints

Available only for DCS Redis 4.0 and later instances and not for the enterprise edition.
Unavailable for Proxy Cluster instances.
The instance must be in the Running state. The target subnet has sufficient IP addresses.
An instance's VPC cannot be changed.

Impacts

The instance's IP address will be changed and the existing service connections will be interrupted. Note:

Ensure that there is no service traffic on the instance. Change the subnet after client traffic is switched.
The client needs to be restarted for access to Redis at a connection address (domain name).
The client needs to be restarted for access to Redis at the new IP address.

Procedure

Log in to the DCS console.
Click in the upper left corner of the console and select the region where your instance is located.
In the navigation pane, choose Cache Manager.
Click the name of the desired instance for which to switch the subnet.
In the Network area, click next to Subnet.
In the dialog box displayed, select the new subnet.
- The number of available IP addresses of the selected subnet is prompted. Ensure that it is sufficient.
- When IPv6 is enabled for the instance, enable IPv6 for the new subnet.
Click OK.

When the background task is in the Successful state, the subnet is changed.