After switching a Tair (Redis OSS-compatible) instance from a classic network to a Virtual Private Cloud (VPC), you can retain the classic network endpoint for a transition period. If you need more time to migrate your applications, extend the retention period by updating the expiration date in the console.
Prerequisites
Before you begin, ensure that you have:
A classic network endpoint already retained on the instance. The endpoint is created automatically when you switch the network type from classic network to VPC
Usage notes
The new expiration date takes effect immediately after you save the change. For example, if you extend the retention period by 14 days on August 15, the endpoint is released on August 29 — not 14 days from the original expiration date.
You can update the expiration date multiple times.
Extend the retention period
Log on to the Tair (Redis OSS-compatible) console. In the top navigation bar, select the region where the instance is deployed. Find the instance and click its ID.
On the right side of the Connection Information section, click Change Expiration Date next to Retained Classic Network Endpoint.
In the panel, specify a new expiration date and click OK.
API reference
| Operation | Description |
|---|---|
| ModifyInstanceNetExpireTime | Modifies the expiration date of a classic network endpoint |
What's next
EOL notice for Tair (Redis OSS-compatible) instances in the classic network