-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Terraform kafka provider does not support AWS_MSK_IAM for sasl_mechanism #278
Comments
@leenapatranbs and if the MSK is also configured to enable Unauthenticated access in addition to enabling IAM? The module will work? |
@taliv-upstream According to the AWS docs here that isn't possible, IAM/SASL requires TLS for client-broker and encrypted broker-broker communication. |
Hi, Are there any plans to add support for IAM authentication? |
@TFiroozian There's been a PR #242 open for a while, but it looks like it could use some love. |
+1 to that. |
Also reported in #218. |
I think this can be closed since #372 has been released. Although the docs haven't been updated yet. |
#372 doesn't seem to use IAM role we need to export AWS_CREDS to use SASL_IAM |
As per the link https://github.com/aws/aws-msk-iam-auth#details
AWS_MSK_IAM can be used as one of sasl_mechanism for create topic using IAM role. However as per the terraform documentation for Kafka provider it does not support this value.
The text was updated successfully, but these errors were encountered: