Accessing Other Tencent Cloud Database Resources via Private Network
Overview
If you want your CloudBase Run service to securely access other resources in your Tencent Cloud account — such as MySQL, Redis, Kafka, or even services deployed on CVM instances — you can use the Private Network Interconnection feature of CloudBase Run. Once enabled, you can access resources within the VPC via their private IP addresses.
Benefits of Private Network Interconnection
- High Security: Data transmission stays off the public internet, reducing security risks
- Excellent Performance: Low latency, high bandwidth, and fast access speeds on the private network
- Cost Savings: Avoids public network traffic fees
- Stable and Reliable: Private network environments are more stable with less network fluctuation
Configure Private Network Interconnection
Learn how to configure and enable private network interconnection in CloudBase Run
Access Database Services
Detailed examples for connecting to various Tencent Cloud database services via private network
Access Other Services
Connect to other Tencent Cloud resources such as CVM and container services
Best Practices
Security configuration, performance optimization, and troubleshooting for private network interconnection
Configure Private Network Interconnection
Prerequisites
- Your Tencent Cloud account already has a VPC network configured
- The target resource (e.g., database instance) is deployed within that VPC
- CloudBase Run and the target resource are in the same region
Configuration Steps
1. Enable Private Network Interconnection
Configure private network interconnection in the CloudBase Run console:
- Log in to the [CloudBase Console]
- Select the corresponding CloudBase Run service, go to the Service Configuration page, and click Edit
- In the Private Network Settings section
- Select the target VPC and subnet
- Save the configuration
2. Configure Security Groups
Ensure security group rules allow CloudBase Run to access the target resource:
# Example: Allow CloudBase Run to access MySQL (port 3306)
Inbound Rules:
- Protocol: TCP
- Port: 3306
- Source: CIDR of the subnet where CloudBase Run resides (e.g., 10.0.1.0/24)
# Example: Allow CloudBase Run to access Redis (port 6379)
Inbound Rules:
- Protocol: TCP
- Port: 6379
- Source: CIDR of the subnet where CloudBase Run resides