Hi , This seems to be a connection issue to your broker. Can you check the following:
- Your inbound security group should allow traffic (on port 9196) from the public ipv4 address of your local machine.
- Your client secret is associated with the cluster
- Your client has the necessary kafka-acl permissions to perform create topic operation
Hope this helps.
local configuration setting to sent data from local .Net to MSK cluster through SASL/SCRAM
AWS MSK - Creating a client Machineasked 4 months ago
Local machine cannot access to aws MSK
I cannot connect to AWS RabbitMQ from my local machineasked 8 months ago
I don't have access to quicksightasked 24 days ago
Accessing Running Container on AWS to my local machineasked 2 months ago
Set consumer.isolation.level in MSK Connect (sink connector)asked 3 months ago
Using MSK as trigger to a Lambda with SASL/SCRAM Authenticationasked 4 months ago
Send Data from local .Net application to AWS MSK?Accepted Answer
Cannot directly set up BatchGetItem step inside a State Machineasked 4 months ago