tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Changing Network

PDF
Focus Mode
Font Size
Last updated: 2026-01-29 17:47:37
This document describes how to change the network of TDSQL-C for MySQL in the console.

Overview

TDSQL-C for MySQL supports VPC, which is capable of offering a diversity of smooth services. On this basis, it provides the cluster network change feature to help you manage network connectivity with ease.

Notes

When the network is changed, all of the cluster's private IPs are automatically replaced with new ones. You should modify the client program accordingly in time.
You can specify the remaining validity period of the old IPs in the console. The period is 24 hours by default. If you set the period to 0 hours, the old IPs will be released immediately after the network is changed.
The new VPC and subnet should be in the region of the cluster.

Subnet description

A subnet is a logical network space in a VPC. You can create subnets in different AZs in the same VPC, which communicate with each other over the private network by default. Even if you select a subnet IP in another AZ in the region of the cluster, the network latency will not be increased because the actual business connection adopts nearby access.

Directions

On the cluster management page, proceed according to the actually used view mode:
Tab view
List view
1. Log in to the TDSQL-C for MySQL console.
2. Click the target cluster in the cluster list on the left to enter the cluster management page.
3. On the cluster management page, click Change Network after Network.

4. In the Change Network pop-up window, select a network, set Valid Hours of Old IPs, and click OK.


5. After changing the network, you can view the new network in the Network section on the cluster management page, and view the new private network address in the Basic Info section on the cluster details page.
1. Log in to the TDSQL-C for MySQL console.
2. Select the region at the top and click the cluster ID in the cluster list or Manage in the Operation column to enter the cluster management page.
3. Click on the instance list, select the target instance (either read-write or read-only), and click on its instance ID to enter the instance details page.
4. On the Instance Details page, click Change Network in Connection Info > Network.

5. In the Change Network pop-up window, select a network, set Valid Hours of Old IPs, and click OK.

6. After changing the network, you can view the new network in the Network section and the new private network address in the Connection Info section on the details page.

Related APIs

API
Description
This API (SwitchClusterVpc) is used to replace the cluster's vpc.

Help and Support

Was this page helpful?

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

Feedback