Skip to content
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

Fix AWS_MSK_IAM configuration handling #223

Merged
merged 1 commit into from
May 31, 2021

Conversation

rtimush
Copy link

@rtimush rtimush commented May 31, 2021

There seems to be a typo that breaks AWS_MSK_IAM authentication.

@weeco
Copy link
Contributor

weeco commented May 31, 2021

Hey @rtimush ,
good find! Unfortunately I never had the chance to actually test it. Do you have a chance to give it a shot and possibly report back whether it works?

@weeco weeco merged commit 99480a7 into redpanda-data:master May 31, 2021
@rtimush rtimush deleted the aws-msk-iam branch May 31, 2021 21:01
@rtimush
Copy link
Author

rtimush commented May 31, 2021

Hey @weeco. I tried quay.io/cloudhut/kowl:master-99480a7e and unfortunately it still didn't work for me with an Access denied: SASL_AUTHENTICATION_FAILED: SASL Authentication failed. error.

@twmb
Copy link
Contributor

twmb commented May 31, 2021

@rtimush how are you trying to access the cluster? from a local ec2 instance, or from your laptop? what is your IAM policy, as well? I know when I tested this, the default policies are kafka:*, but MSK wants kafka-cluster:*, which took a bit to find ...

@rtimush
Copy link
Author

rtimush commented May 31, 2021

I indeed made a mistake in the resources section of the IAM policy. Everything works, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants