Unable to connect with AWS MSK cluster using KAFKA-UI. Clsuter was enabled with SASL/SCRAM authentication.

[apunati]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running master-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

When we try to connect with aws msk cluster using KAFKA-UI its failing. when we verified logs it throwing this error .
" ERROR [kafka-admin-client-thread | kafka-ui-admin-1714391696-80] o.a.k.c.u.KafkaThread: Uncaught exception in thread 'kafka-admin-client-thread | kafka-ui-admin-1714391696-80':
java.lang.OutOfMemoryError: Java heap space
2024-04-29 11:54:56,600 ERROR [parallel-1] c.p.k.u.s.StatisticsService: Failed to collect cluster lacp-development-msk info
java.lang.IllegalStateException: Error while creating AdminClient for Cluster lacp-development-msk".

our My MSK cluster enabled with SASL/SCRAM

Expected behavior

We should able to connect with MSK cluster using broker endpoints then able to view the cluster details like topics, broker, consumer details etc.

Your installation details

I just used the docker which was given in repository.

Steps to reproduce

• Need to create docker conatiner using the docker image in aws ec2. because we can access MSK in private endpoint. MSK and ec2 instance should be in same vpc. Also msk should be enabled with SASL/SCRAM Authentication
• After creating container need to access application using ec2 public IP on browser.
• Then verify are you able to connect or not.

Screenshots

Logs

kafka logs.txt

Additional context

No response

[github-actions]

Hello there apunati! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

[apunati]

we need team assistance on the above issue.