Esta página aún no está disponible en su idioma local. Estamos trabajando arduamente para agregar más versiones de idiomas. Gracias por tu apoyo.
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of Using RocketMQ
- Creating a User and Granting DMS for RocketMQ Permissions
- 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 SSL of a RocketMQ Instance
- Modifying RocketMQ Specifications
- Migrating Metadata
- Viewing Monitoring Metrics and Configuring Alarms
- Viewing RocketMQ Audit Logs
- Best Practices
- Developer Guide
- API Reference
- SDK Reference
- FAQs
- Videos
Enabling RocketMQ ACL
RocketMQ instances support precise identification of producers and consumers through ACL (Access Control List)-based permission management. When ACL is enabled, message production and consumption require authentication.
Notes and Constraints
Enabling ACL will disconnect clients without authentication configuration.
Prerequisite
A RocketMQ instance has been purchased.
Enabling RocketMQ ACL
- Log in to the console.
- Click
in the upper left corner to select a region.
NOTE:
Select the region where your RocketMQ instance is located.
- Click
and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ. - Click a RocketMQ instance to go to the instance details page.
- In the Connection area, click
next to ACL to enable ACL.
When ACL is enabled, Users is displayed in the navigation pane. You can configure ACL users by referring to Configuring RocketMQ ACL Users.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
