Configuration of an ACL Policy for a Topic Causes the Failure of Other Products' Integration Capabilities
Last updated:2026-01-20 17:19:22
Configuration of an ACL Policy for a Topic Causes the Failure of Other Products' Integration Capabilities
Last updated: 2026-01-20 17:19:22
Overview
The configuration of an ACL policy for a topic causes the failure of other products' integration capabilities.
Possible Causes
By default, a topic is not configured with an ACL, allowing free access within the same Virtual Private Cloud (VPC). If permission control is required within VPC, configure an ACL. See Configuring an ACL Policy.
When an ACL policy is added to a topic, it will block all other non-compliant requests from accessing the topic, including calls from other cloud products integrated with CKafka (for example: Cloud Log Service (CLS) log shipping, Serverless Cloud Function (SCF) message dumping, and consumption by big data EMR components).
From a business perspective, once an ACL is set to ensure security, the business does not want non-compliant clients to access Kafka data. Therefore, it is reasonable for such access to be denied.
Solutions
Before adding an ACL policy to a topic, be sure to use business information or console monitoring information to determine whether the topic is used in other scenarios. Otherwise, it may cause issues with other integrated features.
To address this issue, if you must implement ACL policy management, it is recommended that you produce messages to a new topic for permission assignment rather than reusing the original topic.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback