-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for AWS IAM authentication #126
base: main
Are you sure you want to change the base?
Conversation
Any news on this? |
Any update on this ? |
Hey @andsel, is there anything I can do to get this merged? I'd be happy to resolve the conflicts and update the PR but not sure if there's any intention from your side to merge it. Unfortunately, I haven't received any feedback since I opened the PR, although I believe this would be a useful addition to the plugin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @korsosa
the PR seem promising, however would be better to split in 2:
- the first PR would introduce just the setting
sasl.client.callback.handler.class
, which is the abstract way to provide any SASL client handler - another one for the specific dependencies related to AWS AIM
Hi @korsosa, will you be working on this? |
AWS MSK has an optional IAM auth feature that enables to use AWS IAM policies for managing authentication/authorization to Kafka resources instead of Kafka ACLs. More information in the AWS MSK documentation.
This change
AWS_MSK_IAM
sasl.client.callback.handler.class
to allow providing custom SASL callback handlersbuild.gradle
to export all Jar dependencies and add them to the jars file. If a transitive dependency should not be exported, thetransitive=false
flag can be used.Tested both input and output on an AWS EC2 machine with AWS MSK (Kafka version 2.6.2) and Logstash 8.2.3.
Usage as input/output:
This PR also fixes the issue #124
Closes: #124