-
Notifications
You must be signed in to change notification settings - Fork 68
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
unable to connect to aws-msk using library #64
Comments
The files in
|
facing the same issue on on macOS it was working then stopped suddenly with no changes |
Facing the same issue on a Amazon Linux EC2 |
Had a similar issue. The From your example, you placed it in the root:
In order to get the file and place it inside this folder, I simply ran the following command in Make sure you're in You should now have Find more here, step number 7: https://docs.aws.amazon.com/msk/latest/developerguide/create-topic.html |
Anyone work out where to put this thing on a macos homebrew install? |
@shayneoneill I got this working by adding the file to this homebrew path: |
@jeffreygolden I'm trying to do the same on my MAC but dint have success yet. Here's what I have: current working dir:
I have the jar file in this dir:
my client.properties
Trying to connect but still same issue:
What could I be missing here? |
We are facing the same issue when we are trying to use the IAM authentication from kafka connect. We are using the
We are running our |
@Devarsh23 we are facing the same issue, have you found a solution for this? |
error getting :
how i loaded classpath:
export CLASSPATH=/home/ec2-user/aws-msk-iam-auth-1.1.3-all.jar
logged in as user root. Using instance profile with kafka full access.
client.properties:
executing from dir:
home/ec-user:
java version:
[root@ip-192-168-130-35 bin]# java --version openjdk 11.0.14.1 2022-02-08 LTS OpenJDK Runtime Environment Corretto-11.0.14.10.1 (build 11.0.14.1+10-LTS) OpenJDK 64-Bit Server VM Corretto-11.0.14.10.1 (build 11.0.14.1+10-LTS, mixed mode)
command:
not sure what I am mistaking here.
The text was updated successfully, but these errors were encountered: