@@ -218,14 +218,11 @@ The full list is under the `./config-examples/` folder:
218218 "brokers" : [" kafka-xxxxx-aiven-kafka.aivencloud.com:12345" ],
219219 "clientId" : " superstream-analyzer" ,
220220 "vendor" : " aiven" ,
221- "useSasl" : true ,
222- "sasl" : {
223- "mechanism" : " SCRAM-SHA-256" ,
224- "username" : " avnadmin" ,
225- "password" : " YOUR_AVNADMIN_PASSWORD"
226- },
221+ "useSasl" : false ,
227222 "ssl" : {
228- "ca" : " ./path/to/ca.pem"
223+ "ca" : " path/to/ca.pem" ,
224+ "cert" : " path/to/service.cert" ,
225+ "key" : " path/to/service.key"
229226 }
230227 },
231228 "file" : {
@@ -549,6 +546,27 @@ The tool includes comprehensive validation that will:
549546
550547### Common Issues
551548
549+ ** Missing Vendor Field Error**
550+ - ** Error** : "Missing 'vendor' field in kafka configuration"
551+ - ** Solution** : Add the appropriate vendor field to your configuration:
552+ - AWS MSK IAM: ` "vendor": "aws-msk" `
553+ - Confluent Cloud: ` "vendor": "confluent-cloud" `
554+ - Aiven: ` "vendor": "aiven" `
555+ - Apache Kafka: ` "vendor": "apache" `
556+ - Redpanda: ` "vendor": "redpanda" `
557+ - ** Why** : The vendor field tells the tool how to handle vendor-specific authentication mechanisms
558+
559+ ** AWS MSK IAM Authentication Failed**
560+ - ** Error** : "Failed to generate auth token" or "authenticationProvider is not a function"
561+ - ** Solution** :
562+ 1 . Ensure AWS credentials are properly configured:
563+ - Set ` AWS_ACCESS_KEY_ID ` and ` AWS_SECRET_ACCESS_KEY ` environment variables, OR
564+ - Include credentials in config file: ` "accessKeyId" ` and ` "secretAccessKey" `
565+ 2 . Verify the IAM user has proper MSK permissions
566+ 3 . Check that the broker URLs are correct (should use port 9198 for IAM)
567+ 4 . Ensure the region matches your MSK cluster
568+ - ** Why** : AWS MSK IAM requires valid AWS credentials and proper IAM permissions
569+
552570** Connection Timeout**
553571- Verify broker URLs are correct
554572- Check network connectivity
0 commit comments