ClusterConnectionNotFound when portfowarding into AWS

[maujour]

I'm using SSM to portfoward to the cluster configuration endpoint and then setting localhost locally. redis-cli works fine with redis-cli -c -h localhost -p 6379 but with deadpool-redis I get No connections found for multi-node operation- ClusterConnectionNotFound

Any ideas?

[bikeshedder]

Just an educated guess: localhost sometimes means the use of a unix domain socket such as /tmp/redis. Could you give 127.0.0.1 (IPv4) or ::1 (IPv6) as host a try?

Otherwise I don't see why redis-cli can connect to the redis database but deadpool-redis can't. 🤔

[maujour]

Well, it works when deployed in AWS, where it points directly to the cfg endpoint instead of localhost.
I tried a NodeJS package and got same behavior as deadpool-redis. What tricks me is the cli working with localhost and these libraries not.

I would be much appreciated if someone has any clue what I'm doing wrong. Thanks!

Some extra info:
I'm using a bastionhost with SSM.
My cluster is in compatible mode.