tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Changing Networks

PDF
Focus Mode
Font Size
Last updated: 2026-03-18 10:45:57

Network overview

Tencent Cloud offers VPC (recommended) and classic network environments. A VPC is a logically isolated network space that can be customized in Tencent Cloud. Similar to the traditional network run in an IDC, a VPC is where your Tencent Cloud service resources are managed, such as Cloud Virtual Machine, Cloud Load Balancer, and TencentDB for MySQL. The difference between classic network and VPC is as follows:
The classic network is a public network resource pool for all Tencent Cloud users. The private IPs of all CVMs are assigned by Tencent Cloud. You cannot customize IP ranges or IP addresses.
A VPC is a logically isolated network space in Tencent Cloud. In a VPC, you can customize IP ranges, IP addresses, and routing policies, making it more suitable for use cases requiring custom configurations.
A subnet is a network space in a VPC, which carries all the cloud resource deployments. A VPC has at least one subnet. A subnet will be created together with the VPC. You can also create more subnets in a VPC that suit your specific requirements to deploy different businesses.
A subnet is AZ-specific. You can create subnets in different AZs in the same VPC, which communicate with each other over the private network by default.

Notes

You can switch from classic network to VPC but not vice versa.
You can switch from one VPC to another or between subnets in the same VPC.
After the network switch, the new IP address will take effect immediately, and all connections to the original IP address will be closed. The original IP address will be retained for up to 15 days.
Note:
To ensure the service availability and keep your businesses uninterrupted during network switch, update the IP address promptly as needed and be cautious about releasing the old IP address.

Prerequisites

You have created a database instance and configured the classic network or VPC as instructed in Creating Instance.
You have created the target VPC as instructed in Creating VPC.
The database instance is in Running status, with no ongoing tasks.

Changing the network

2. Above the instance list, select the region.
3. In the instance list, find the target instance.
4. Click the target instance ID to enter the Instance Details page.
5. In the Network Info section on the Instance Details page, you can see the network and private IP of the current instance. Click Change Network next to Network.

6. In the Change Network window, configure the new network information and click OK.
Network: Select a VPC and a subnet in the drop-down lists next to Network respectively.
New IP: Select Auto-assign or Designate Address. If you select the latter, then enter a custom IP address in the input box.
Old IP: Set the release time of the old IP. You can select Release Now, Release after 1 day, Release after 2 days, Release after 3 days, Release after 7 days, or Release after 15 days as needed to ensure the business continuity during the network change.

7. Click OK, and wait for the task to complete successfully. On the Instance Details page, in the Network Info section, you can confirm that the network information has been updated successfully.

Related APIs

API
Description
Modifies the network configuration of instance

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback