This document describes how to configure network connections in compute resources to connect the network where the compute resources reside with your private VPC, on-premises IDC, or third-party cloud, and how to enable JDBC / ODBC inbound access for external applications.
Overview
Compute resources in DataBuddy run in a managed VPC by default. To allow them to access data sources such as databases, Kafka, and Oracle in your private VPC, you must first complete network connectivity. DataBuddy provides network configuration in two directions:
|
Outbound (compute resources → data source) | Compute resources access user-side data sources. | Data ingestion, external Catalog, federated analysis |
Inbound (external applications → compute resources) | User-side applications access DataBuddy compute resources through JDBC/ODBC. | BI tools such as PowerBI / Qlik read DataBuddy Catalog. |
The network settings of the platform cluster and the real-time cluster are a prerequisite for successful data ingestion tasks and connectivity tests.
Prerequisites
You have joined the target workspace and have the Can Manage permission on the target compute resource.
You have created the VPC and subnet in Tencent Cloud that the compute resources need to connect to, and reserved sufficient IP addresses in the subnet. Outbound settings consume private IP addresses in your VPC.
Entering Network Settings
1. Select Compute Resources in the left sidebar.
2. Locate the target compute resource in the list, and choose More > Network Settings in the operation column.
3. Go to the Network Settings: ${Resource Name} page. The page contains two tabs: Outbound and Inbound.
Outbound: Compute Resources Accessing User-Side Data Sources
Scenarios
|
Intra-cloud access over private network | Within the user's Tencent Cloud VPC | Access Tencent Cloud RDS MySQL and Kafka |
Hybrid cloud / cross-VPC access | On-premises IDC or VPC in other clouds | Access on-premises Oracle, cross-account ERP systems, and third-party cloud data |
Access through a fixed public network egress | Public network (IP address allowlist) | Access databases and APIs on public networks |
Creating an Outbound Connection
1. When the list on the Outbound Tab is empty, click Create Network Connection.
2. In the pop-up window, configure the following:
|
VPC | Select the VPC to connect. The dropdown list displays "VPC ID (Name)". | Yes |
Subnet | Select a subnet. The dropdown list displays "Subnet ID (Name)". After selection, the number of available IP addresses in the subnet is displayed below. | Yes |
Note:
1. If no suitable VPC or subnet is available in the list, click the link in the prompt below to go to the VPC console and create one. After selecting a VPC and subnet, you can click Refresh on the right to reload them. 2. If the data source is accessed over the public network, the VPC selected here must have public network access capability. For instructions on how to configure VPC access to the public network, see Creating a NAT Gateway. 3. Click OK and wait for the network configuration to complete. This typically takes a few minutes.
4. After the creation is successful, a new record is added to the list, displaying the VPC name/ID, subnet, creator, and creation time. The Create Network Connection button is grayed out, and hovering over it displays "Currently, only one VPC connection is supported."
Deleting an Outbound Connection
Click Delete in the operation column of the record, and confirm the deletion. Deleting the connection affects the network connectivity between the compute resource and the data source. After deletion, the Create Network Connection button becomes available again, and you can connect to another VPC.
Inbound: External Applications Accessing DataBuddy Compute Resources
Scenarios
Use inbound settings when external applications such as PowerBI, Qlik, or third-party reporting tools need to read metadata or business data from the DataBuddy Catalog through the JDBC / ODBC protocol from DataBuddy compute resources.
Creating an Inbound Connection
1. On the Inbound Tab, click Create Network Connection.
2. Configuration:
|
VPC | Select the VPC to open access to. | Yes |
Subnet | Select a subnet. | Yes |
3. Click OK to complete the creation. The list displays information such as the VPC, subnet, IP address and port, creator, and creation time.
Multiple network connections can be created for inbound traffic, allowing applications in different VPCs to connect.
Viewing Inbound Details
Click Details in the operation column of the inbound record. A new window opens and redirects to the Tencent Cloud VPC page, where you can view complete endpoint status, traffic statistics, and other information.
Deleting an Inbound Connection
Click Delete in the operation column of the record, and confirm the deletion.
Warning:
Deleting an inbound connection immediately interrupts all external applications that are accessing compute resources through the endpoint. Synchronize with the business team before deletion.
Integration with Other Modules
Module | Relationship |
| Data source connectivity tests are executed through specified compute resources. If the data source is in a user's private VPC, outbound settings must be completed here first. |
| Test results reflect the actual network reachability between compute resources and data sources. |
| Some cluster types (platform clusters / real-time clusters) support directly selecting a VPC / subnet during creation. |
Use Limits
Only one VPC is supported for outbound traffic: each compute resource can connect to only one VPC in the outbound direction. If data sources are distributed across multiple VPCs, do the following: ① Interconnect the VPCs on the user side through VPC Peering Connection or CCN. ② Or create corresponding compute resources for data sources in different VPCs.
Inbound supports multiple connections: inbound can open access to applications in multiple VPCs at the same time.
Subnet IP Address Occupation: An outbound connection occupies private IP addresses in the user subnet (for ENIs). Ensure that sufficient IP addresses are reserved in the subnet.
Modifying the VPC is not supported: You cannot modify the VPC when editing an outbound connection. To change the VPC, delete the existing connection and create a new one.
FAQs
Q1: The connectivity test keeps failing. How do I troubleshoot this?
Troubleshoot in the following order: ① Check whether the VPC/subnet of the outbound connection contains the network segment where the data source resides. ② Check whether the subnet security group allows traffic on the data source port (such as MySQL 3306 and Kafka 9092). ③ Check whether the allowlist on the data source side contains the subnet CIDR. ④ Check whether the data source service itself is healthy.
Q2: How is Oracle in an on-premises IDC connected?
First, connect your on-premises IDC to a Tencent Cloud VPC through a Tencent Cloud VPN gateway or Direct Connect gateway. Then, select the Tencent Cloud VPC in the DataBuddy outbound connection to access Oracle in the IDC.
Q3: Will data residue remain after a network connection is deleted and recreated?
No. Deletion is physical, and new ENIs and IPs are allocated after recreation. However, complete all in-progress tasks before deletion to prevent data from not being persisted.
Q4: Is the IP address of an inbound connection fixed?
Inbound connections are implemented through Tencent Cloud PrivateLink. After you create an endpoint on the user side, you will obtain a fixed endpoint IP address that can be used as the connection address for external applications.
References