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
DokumentasiTDMQ for RabbitMQUser GuideConfiguring the Account PermissionGranting Resource-Level Permission to Sub-account

Granting Resource-Level Permission to Sub-account

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-01-05 10:03:28

Scenarios

You can use the policy feature of the Cloud Access Management (CAM) console to grant the permissions for RabbitMQ resources owned by the root account to sub-accounts. Sub-accounts that obtain the permissions will gain access to those resources. This document takes granting permissions for the resources of a cluster to sub-accounts as an example. The operation steps for other types of resources are similar.

Prerequisites

You have created sub-accounts for employees using the Tencent Cloud root account. For detailed operations, see Creating a Sub-account.
At least one RabbitMQ cluster is available.

Operation Steps

Step 1: Obtaining the ID of the RabbitMQ Cluster

1. Use the root account to log in to the TDMQ for RabbitMQ console.
2. In the left sidebar, select Cluster. Select the target region and copy the ID of the target cluster.


Step 2: Creating an Authorization Policy

1. Log in to the CAM console.
2. In the left sidebar, select Policies, click Create a Custom Policy, and set the policy creation method to Create by Policy Builder.
3. In the visualized policy generator, keep the Effect as Allow and select the Service. The following describes how to select a service:
Managed Edition: Enter TDMQ to filter, and select Tencent Distributed Message Queue (tdmq) from the results.
Serverless Edition: Enter trabbit to filter, and select RabbitMQ Serverless (trabbit) from the results.
4. In Action, select All Actions. You can also select an appropriate operation type based on your actual business needs.
Note:
Certain APIs currently do not support resource authentication. For the APIs that support resource authorization, those displayed on the console page shall prevail.
5. In the Resource section, select Specific resources, and locate the cluster resource type. You can check Any resource of this type (authorize all cluster resources) on the right, or click Add a six-segment resource description (authorize specific cluster resources). In the pop-up sidebar dialog box, enter the cluster ID in the Resource Prefix field.

6. In the Condition section, select whether to specify the source IP address based on actual business requirements. After a source IP address is specified, access to the specified operation is allowed only when the request comes from the specified IP address range.
Click Next to set the policy name. The policy name is automatically generated by the console, with the default name of "policygen", with the suffix number generated based on the creation date. You can customize it.
7. Click Select User or Select User Group to grant resource permissions.

8. Click completed, and the sub-accounts granted resource permissions now have the ability to access the relevant resources.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan