tencent cloud

TDMQ for Apache Pulsar

Release Notes and Announcements
Release Notes
Cluster Version Updates
Product Announcements
Product Introduction
Introduction and Selection of the TDMQ Product Series
What Is TDMQ for Apache Pulsar
Strengths
Scenarios
How It Works
Product Series
Version Support Instructions for Open-Source Apache Pulsar
Comparison with Open-Source Apache Pulsar
High Availability
Quotas and Limits
Basic Concepts
Billing
Billing Overview
Pricing
Billing Examples
Renewal
Viewing Consumption Details
Overdue Payments
Refund
Getting Started
Getting Started Guide
Preparations
Using the SDK to Send and Receive General Messages
Using the SDK to Send and Receive Advanced Feature Messages
User Guide
Usage Process Guide
Configuring the Account Permission
Creating a Cluster
Configuring the Namespace
Configuring the Topic
Connecting to a Cluster
Managing the Cluster
Querying Messages and Traces
Cross-Region Replication
Viewing Monitoring Data and Configuring Alarm Rules
Use Cases
Client Usage
Abnormal Consumer Isolation
Traffic Throttling Mechanisms
Transaction Reconciliation
Message Idempotence
Message Compression
Migration Guide
Single-Write Multiple-Read Cluster Migration Solutions
Hitless Migration from Virtual Cluster to Pro Cluster
SDK Reference
API Overview
SDK Reference
SDK Overview
Recommended SDK Configuration Parameters
TCP Protocol (Apache Pulsar)
Security and Compliance
Permission Management
Deletion Protection
CloudAudit
FAQs
Monitoring
Clients
Agreements
Service Level Agreement
TDMQ Policy
Contact Us
Glossary

Network Connection Instructions

PDF
Focus Mode
Font Size
Last updated: 2025-12-24 14:59:00
TDMQ for Apache Pulsar supports both private and public network access, with connection requirements varying depending on the network type.

Connection Method Description

Connection Method
Connection Description
Reference Documentation
Private Network Connection
If the client and the Pulsar cluster are deployed within the same Virtual Private Cloud (VPC), they can communicate over the private network by default, without requiring any additional configuration.
If the client and the Pulsar cluster are deployed in different VPCs, since VPCs are logically isolated from each other, they cannot communicate directly. To enable cross-network communication, you can use Cloud Connect Network (CCN) to achieve VPC interconnection across different regions under the same account.
Public Network Connection
A dedicated public network route needs to be established, allowing clients to connect to the Pulsar cluster over the public network. Since public networks are accessible from any network environment, security policies need to be configured to ensure secure connections.
Normally, it is recommended that you prioritize private network access to achieve lower network latency, higher transmission bandwidth, and better security isolation, especially for core businesses in production environments. Public network access can be enabled when necessary, for example, when your service needs to be publicly accessible or during development and debugging from public networks. When public network access is enabled, it is recommended that you configure an allowlist policy to strictly restrict access by IP addresses to ensure data security.

Security Group Requirements

Ensure that the security group for your test program allows TCP traffic on ports 6000-7000 (communication ports) and 8080 (the addressing port for routing access). For specific steps, see Creating a Security Group.

Help and Support

Was this page helpful?

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

Feedback