Skip to content
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

[Inquiry] ACL issue not returning proper error message #3026

Open
hqkhan opened this issue Jan 29, 2025 · 1 comment
Open

[Inquiry] ACL issue not returning proper error message #3026

hqkhan opened this issue Jan 29, 2025 · 1 comment
Labels
java issues and fixes related to the java client Unatriaged user issue Issue open by user and wasn't triaged yet User issue Issue openned by users Users Pain An issue known to cause users pain, generaly open by the user.

Comments

@hqkhan
Copy link

hqkhan commented Jan 29, 2025

Inquiry

Setup

I was on AWS' MemoryDB 7.1.1 cluster. I'm using Valkey-glide to create a redis connection. Here's a snippet:

            NodeAddress nodeList = NodeAddress.builder().host(this.host).port(connectionConfig.redisPort()).build();
            GlideClusterClientConfiguration glideConfig = GlideClusterClientConfiguration
                .builder()
                .address(nodeList)
                .credentials(getIAMcredentials(awsCredentialsProvider))
                .useTLS(USE_TLS)
                .build();
            GlideClusterClient client = GlideClusterClient.createClient(glideConfig).get();

Prior to this, I was using Glide's Standalone client GlideClient. This issue popped up when I updated my codebase to use GlideClusterClient.

Issue

When I tried creating this client, I could see an error of:

client creation - Connection error: Cluster(No topology views found- ResponseError)"

The above was in my cloudwatch logs. This error stems from here. I eventually discovered that my ACL lacked permissions to run cluster slots command. Adding this to my ACL fixed the issue.

The main problem with this is that the error didn't come accompanied with NOPERM: that would point me to my ACL string. I've had other issues like missing ping capabilities in my ACL but I did get NOPERM: errors at that time.

Language

Java

Language Version

17

Engine Version

MemoryDB 7.1.1

Operating System

AL2

Additional Technical Information

No response

@Muhammad-awawdi-amazon
Copy link
Collaborator

Thanks for opening the issue.
We will take a look and add it to our workplan :)

@Muhammad-awawdi-amazon Muhammad-awawdi-amazon added java issues and fixes related to the java client Users Pain An issue known to cause users pain, generaly open by the user. Unatriaged user issue Issue open by user and wasn't triaged yet User issue Issue openned by users labels Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
java issues and fixes related to the java client Unatriaged user issue Issue open by user and wasn't triaged yet User issue Issue openned by users Users Pain An issue known to cause users pain, generaly open by the user.
Projects
None yet
Development

No branches or pull requests

2 participants