tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary

Enabling Public Network Access Through CLB

PDF
Focus Mode
Font Size
Last updated: 2025-04-27 14:20:34
TencentDB for MySQL supports both private and public network addresses, with the former enabled by default for you to access your instance over the private network and the latter enabled or disabled as needed. To access your database instance from a Linux or Windows CVM instance over the public network, you can enable the public network address. You can also enable public network access through CLB, but you must configure security group rules in this case.
This document describes how to enable public network access through CLB and connect to an instance through MySQL Workbench.

Prerequisites

You have applied to use the real server feature. Currently, this feature is in beta testing. To experience this feature, submit a ticket for application.
Note:
Enabling the public network services through CLB is exclusively applicable when the CLB instances and the MySQL instances belong to the same VPC network. It is currently not supported for instances across different VPC networks.

Step 1. Purchase a CLB instance

Note:
If you already have a CLB instance in the same region as TencentDB for MySQL, skip this step.
Go to the CLB purchase page, select the configuration, and click Buy Now.
Note:
Region: You need to select the region where the TencentDB for MySQL instance is.

Step 2. Configure the CLB instance

The following describes how to configure the CLB instance in the same VPC as the database instance and in a different VPC respectively.

Scenario: Deploying the CLB instance in the same VPC as the TencentDB for MySQL instance

1. Enable cross-VPC access so that the CLB instance can be bound to another private IP. a. Log in to the CLB console, select the region, and click the target instance ID in the instance list to enter the instance management page. b. On the Basic Info page, click Configure in the Real Server section. c. In the pop-up window, click Submit.
2. Configure a public network listener port. a. Log in to the CLB console, select the region, and click the target instance ID in the instance list to enter the instance management page. b. On the instance management page, select the Listener Management tab and click Create below TCP/UDP/TCP SSL Listener. c. In the pop-up window, complete the settings and click Submit.

Step 3. Bind a TencentDB for MySQL instance

1. After creating the listener, click it in Listener Management and click Bind on the right.
2. In the pop-up window, select Other Private IPs as the object type, enter the IP address and port of the TencentDB for MySQL instance, and click OK.
Note:
The login account must be a standard account (bill-by-IP). If binding fails, submit a ticket for assistance.

Step 4. Configure the TencentDB for MySQL security group

1. Log in to the TencentDB for MySQL console and select a region. In the instance list, click an instance ID or Manage in the Operation column to enter the instance management page.
2. On the instance management page, select the Security Group tab, click Configure Security Group, configure the security group rule to open all ports, and confirm that the security group allows access from public IPs. For more information on configuration, see TencentDB Security Group Management.


Step 5. Connect to the instance through the MySQL Workbench client

1. Download MySQL Workbench from MySQL Community Downloads and install it.
1. Go to the download page and click MySQL Workbench.
2. Click Download after Windows (x86, 64-bit), MSI Installer.
3. Click No thanks, just start my download.
4. After MySQL Workbench is installed, open it and click the plus sign after MySQL Connections to add the information of the target instance.

5. In the pop-up window, configure the following items and click OK.

Parameter
Description
Connection Name
Name the connection.
Connection Method
Select Standard (TCP/IP).
Hostname
Enter the address of the CLB instance. You can view the VIP information in the basic information on the CLB instance details page.
Port
Enter the port of the CLB instance. You can view the TCP port number in listener management on the CLB instance details page.
Username
Enter the account name of the target MySQL instance, i.e., the account created in Database Management > Account Management on the instance management page.
Store in Vault...
Enter the account password of the target MySQL instance in the Password field and save it.
6. Return to the MySQL Workbench homepage and click the just configured instance to connect to it.

7. The UI after successful connection is as follows:


Help and Support

Was this page helpful?

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

Feedback