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
DocumentationTDSQL-C for MySQLOperation GuideDatabase ProxyManaging Database ProxySwitching Database Proxy Network

Switching Database Proxy Network

PDF
Focus Mode
Font Size
Last updated: 2026-01-29 17:54:31
This document describes how to modify the database proxy network in the TDSQL-C for MySQL console.

Prerequisite

You have enabled the database proxy. For more information, see Enabling Database Proxy.

Notes

Switching the network will cause the database proxy IP address of the instance to change. The maximum retention time can be set to 168 hours, and after the set time has elapsed, the old access IP address will become invalid. Please update the client program promptly.
If Valid Hours of Old IP is set to 0 hours, the IP is released immediately after the network is changed.
You can select only a VPC in the region where the cluster of TDSQL-C for MySQL resides, but you can choose a subnet in any AZ and view its IP range.

Directions

Switching the network will cause the database proxy IP address of the instance to change. The maximum retention time can be set to 168 hours, and after the set time has elapsed, the old access IP address will become invalid. Please update the client program promptly.
1. Log in to the TDSQL-C for MySQL console, select the cluster with the proxy enabled in the cluster list, and click the cluster ID to enter the cluster management page.
2. In the topology diagram under Cluster Management > Cluster Details, hover the mouse pointer over the database proxy section and click Details to enter the database proxy management page. Alternatively, you can directly select the Database Proxy tab on the cluster management page to enter the database proxy management page.
3. On the database proxy page, select Overview > Connection Address > Network and then click the edit icon.

4. In the pop-up dialog box, set the relevant configuration items and click OK.
Select Network: Select a VPC and subnet in the region and AZ where the cluster resides.
Valid Hours of Old IP: Its range is 0–168 hours and default value is 0 hours.
5. After successfully changing the network, you can view the new network under Connection Address.

Related APIs

API
Description
This API (SwitchProxyVpc) is used to replace the database proxy's vpc.
Previous Topic: Adjusting Database Proxy ConfigurationNext Topic: Viewing Database Proxy Monitoring Data

Help and Support

Was this page helpful?

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

Feedback