-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
SASL no TLS and AWS MSK #258
Comments
Try to use
|
@antontreushchenko Same problem unfortunately |
mattia-crypto I have such a security configuration for the cluster, if yours is not like this, then try to do this |
Thanks. However, I see from your screenshot you have unauthenticated access and Plaintext between clients and brokers enabled. Unfortunately, I cannot have that. |
@antontreushchenko on second note, I noticed I had overlooked one of the params in the config you sent. I managed to make it work now with this:
|
I'm bit curious to know,, why you guys are using private port like 9096 ?? it's a private endpoint port for SASL/SCRAM. |
Hi,
I am unable to use the provider with an AWS MSK cluster configured with SASL:
I keep seeing the following on
terraform apply
:when trying to create:
The text was updated successfully, but these errors were encountered: