- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Process of Using RocketMQ
- Permissions Management
- Buying a RocketMQ Instance
- Configuring a Topic
- Accessing an Instance
- Managing Messages
- Managing Consumer Groups
-
Managing Instances
- Viewing and Modifying Basic Information of a RocketMQ Instance
- Viewing Background Tasks of a RocketMQ Instance
- Configuring Tags for a RocketMQ Instance
- Exporting RocketMQ Instances
- Diagnosing a RocketMQ Instance
- Restarting Brokers of a RocketMQ Instance
- Deleting a RocketMQ Instance
- Configuring RocketMQ Recycling Policies
- Configuring SSL of a RocketMQ Instance
- Enabling Flexible TPS for a RocketMQ Instance
- Adjusting Messages Sent/Received of a RocketMQ Instance
- Modifying RocketMQ Specifications
- Migrating Metadata
- Testing Instance Performance
- Viewing Monitoring Metrics and Configuring Alarms
- Viewing RocketMQ Audit Logs
- Best Practices
- Developer Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
APIs V2 (Recommended)
- Lifecycle Management
-
Consumer Group Management
- Querying the Consumer Group List
- Creating a Consumer Group or Batch Deleting Consumer Groups
- Batch Modifying Consumer Groups
- Deleting a Consumer Group
- Querying a Consumer Group
- Modifying a Consumer Group
- Querying the Consumer Group List or Details
- Resetting the Consumer Offset
- Querying the Consumer List
- Topic Management
- Message Management
- User Management
- Metadata Migration
- Managing Parameters
- Tag Management
- Diagnosing an Instance
- Specification Modification Management
- Managing Instances
- Managing Background Tasks
- Other APIs
- Example Applications
- Permissions and Supported Actions
- Historical APIs
- Appendix
- Change History
- SDK Reference
- FAQs
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- Permissions Management
- Preparing Required Resources
- Buying an Instance
- Accessing an Instance
- Managing Instances
- Managing Topics
- Querying Messages
- Managing Consumer Groups
- Managing Users
- Managing Dead Letter Queues
- Diagnosing an Instance
- Migrating Metadata
- Monitoring
- Auditing
- FAQs
- Change History
- API Reference (ME-Abu Dhabi Region)
- Developer Guide(ME-Abu Dhabi Region)
-
User Guide (Paris Region)
- Service Overview
- Getting Started
- Permissions Management
- Preparing Required Resources
- Creating an Instance
- Accessing an Instance
- Managing Instances
- Managing Topics
- Managing Messages
- Managing Consumer Groups
- Managing Users
- Managing Dead Letter Queues
- Diagnosing an Instance
- Migrating Metadata
- Monitoring
- Auditing
- FAQs
- Change History
- API Reference (Paris Region)
-
User Guide (Kuala Lumpur Region)
- Service Overview
- Getting Started
- Permissions Management
- Preparing Required Resources
- Buying an Instance
- Accessing an Instance
- Managing Instances
- Managing Topics
- Managing Messages
- Managing Consumer Groups
- Managing Users
- Managing Dead Letter Queues
- Diagnosing an Instance
- Migrating Metadata
- Monitoring
- Auditing
- FAQs
- Change History
-
API Reference (Kuala Lumpur Region)
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- APIs V2 (Recommended)
- Permissions and Supported Actions
- Appendix
- Change History
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Show all
Copied.
Concepts
- Account
An account has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. The account is a payment entity and should not be used directly to perform routine management. For security purposes, create IAM users and grant them permissions for routine management.
- IAM user
An Identity and Access Management (IAM) user is created using an account to use cloud services. Each IAM user has its own identity credentials (password and access keys).
The account name, username, and password will be required for API authentication.
- Region: A region is a geographic area in which cloud resources are deployed. Availability zones (AZs) in the same region can communicate with each other over an intranet, while AZs in different regions are isolated from each other. Deploying cloud resources in different regions can better suit certain user requirements or comply with local laws or regulations.
- An AZ contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, compute, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to support cross-AZ high-availability systems.
- Project
Projects group and isolate resources (including compute, storage, and network resources) across physical regions. A default project is provided for each region, and subprojects can be created under each default project. Users can be granted permissions to access all resources in a specific project. For more refined access control, create subprojects under a project and purchase resources in the subprojects. Users can then be assigned permissions to access only specific resources in the subprojects.
- Enterprise project
Enterprise projects group and manage resources across regions. Resources in enterprise projects are logically isolated from each other. An enterprise project can contain resources of multiple regions, and resources can be added to or removed from enterprise projects.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
