tencent cloud

TDMQ for RabbitMQ

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Introduction and Selection of the TDMQ Product Series
What Is TDMQ for RabbitMQ
Strengths
Use Cases
Description of Differences Between Managed Edition and Serverless Edition
Open-Source Version Support Description
Comparison with Open-Source RabbitMQ
High Availability
Use Limits
TDMQ for RabbitMQ-Related Concepts
Regions
Related Cloud Services
Billing
Billing Overview
Pricing
Billing Example
Convert to Monthly Subscription from Hourly Postpaid
Renewal
Viewing Consumption Details
Overdue Payments
Refund
Getting Started
Getting Started Guide
Step 1: Preparations
Step 2: Creating a RabbitMQ Cluster
Step 3: Configuring a Vhost
Step 4: Using the SDK to Send and Receive Messages
Step 5: Querying a Message
Step 6: Deleting Resources
User Guide
Usage Process Guide
Configuring the Account Permission
Creating a Cluster
Configuring a Vhost
Connecting to the Cluster
Managing Messages
Configure Advanced Feature
Managing the Cluster
Viewing Monitoring Data and Configuring Alarm Policy
Use Cases
Use Instructions of Use Cases
RabbitMQ Client Use Cases
RabbitMQ Message Reliability Use Cases
Usage Instructions for MQTT Protocol Supported by RabbitMQ
Migrate Cluster
Migrating RabbitMQ to Cloud
Step 1. Purchasing a TDMQ Instance
Step 2: Migrating Metadata to the Cloud
Step 3: Enabling Dual Read-Write
API Reference (Managed Edition)
API Overview
API Reference (Serverless Edition)
History
Introduction
API Category
Making API Requests
Relevant APIs for RabbitMQ Serverless PAAS Capacity
RabbitMQ Serverless Instance Management APIs
Data Types
Error Codes
SDK Documentation
SDK Overview
Spring Boot Starter Integration
Spring Cloud Stream Integration
Java SDK
Go SDK
Python SDK
PHP SDK
Security and Compliance
Permission Management
Network Security
Deletion Protection
Change Records
CloudAudit
FAQs
Service Level Agreement
Contact Us

SDK Overview

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-01-04 15:13:50
TDMQ for RabbitMQ is fully compatible with the AMQP 0-9-1 protocol and all components and concepts of open-source RabbitMQ. This document mainly introduces the collection of RabbitMQ cluster connection information, such as obtaining RabbitMQ cluster access points as well as usernames and passwords for accessing the cluster, and provides demo examples and use instructions for SDKs in various languages.

SDK List

Client Network Environment Description

Clients can connect to and access a RabbitMQ cluster through the following three network methods:
1. Direct access within the same Virtual Private Cloud (VPC)
Clients and RabbitMQ clusters are deployed within the same VPC, and the network is interconnected by default. You can directly use the VPC access point for network access.
2. Cross-VPC communication through Cloud Connect Network (CCN)
Clients and RabbitMQ clusters are deployed in different VPC networks. Since VPC networks are logically isolated from each other, they cannot communicate directly. To enable cross-network communication, you can use CCN to achieve VPC interconnection across different regions under the same account.
3. Public network access
Clients deployed in other network environments or in different regions from the RabbitMQ clusters can establish a public network route to access the cluster through the public network access point.
For more information about network environments, see Network Connection Requirements.

Obtaining Connection Information

You need to log in to the TDMQ for RabbitMQ console to obtain the following connection information.
1. Cluster access point address and port information.
The cluster access point address can be obtained from the Client Access module on the basic cluster information page. Different access points can be selected based on different network types.

2. Username and password for accessing the cluster. Ensure that the user has already been granted the corresponding access permissions.
The username can be obtained from the user management page in the console, and the password is the one you set when creating the user.

3. Vhost name.
It can be obtained from the vhost list page in the console.

4. Exchange/Queue name.
It can be obtained from the corresponding exchange and queue resource management page in the console.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan