Kafka ACLs
This page describes the Kafka ACLs prerequisites for the Lenses Agent if ACLs are enabled on your Kafka clusters.
When your Kafka cluster is configured with an authorizer which enforces ACLs, the Agent will need a set of permissions to function correctly.
Grant the Agent only the Kafka operations it needs. Lenses' own IAM model then restricts what each user can do through the Agent. Avoid granting Kafka superuser status: it removes broker-side defence-in-depth if the Agent is ever compromised.
See Minimal Permissions below for the exact ACLs the Agent requires.
Minimal Permissions
The Agent needs permission to manage and access their own internal Kafka topics:
__topology__topology__metrics
kafka-acls \
--bootstrap-server [broker.url:9092] --command-config [client.properties] \
--add \
--allow-principal [User:Lenses] \
--allow-host [lenses.host] \
--operation All \
--topic [topic]It also needs to read and describe permissions for the consumer offsets and Kafka Connect topics —if enabled:
__consumer_offsetsconnect-configsconnect-offsetsconnect-status
This same set of permissions is required for any topic that the agent must have read access.
Additional permissions are needed to produce topics or manage them.
Consumer Groups
Permission to at least read and describe consumer groups is required to take advantage of the Consumer Groups' monitoring capabilities.
Additional permissions are needed to manage groups.
ACLs
To manage ACLs, permission to the cluster is required:
Last updated
Was this helpful?

