Brokers Connection string doesn't show creating cIuster with IAM Access
I have created an MSK cluster with IAM Access Control as a mechanism for authentication and authorization. I can see the broker nodes for my cluster on MSK Console but when I try to write a message to a topic from my kafka client, it gives me error "Broker may not be available".
When I used the cli command i.e. get-bootstrap-brokers, it shows no value for the "BootstrapBrokerStringSaslIam". It gives me nothing at all. Not even a message telling the status of brokers.
I have followed the official documentation for it https://docs.aws.amazon.com/msk/latest/developerguide/iam-access-control.html
However, I can get the ZooKeeper string for my IAM Access Control cluster and can create kafka topics from my kafka client.
I don't know what's happened to my brokers.
Can anyone tell me what should I do?
I had the same issue when I ran
aws kafka get-bootstrap-brokers with an out-of-date aws-cli. Running it with aws-cli/2.2.3 works for me.
Great tip. You will need to update the version of the CLI to use the latest features when they involve API changes.
Yes, it is working now. Thank you njlaw and djwylie :)
How to connect Glue to MSK with IAM authentication?asked 7 months ago
Amazon MSK Authentication and Authorizationasked 6 months ago
IAM Access Analyzer Delegated admin and Org configuration, doesnt pick up root accountasked a month ago
Iam policy for AWS ecs task role for RDS db connectionasked 2 months ago
Aws MSK security behaviour when both IAM and SCRAM enabledAccepted Answerasked 6 months ago
AWS MSK IAM Authentication with MSK Connectasked 5 months ago
Using MSK as trigger to a Lambda with SASL/SCRAM Authenticationasked a month ago
Root cannot view EB environments created by IAMasked 2 years ago
Unable to use IAM permissions to access MSK Brokersasked a year ago
Brokers Connection string doesn't show creating cIuster with IAM AccessAccepted Answerasked a year ago