I'm able to connect to the ElastiCache instance using redis-cli Connection is timing out from RedisInsights in the same port Actual behavior(A short description of what you found) "Could not connect to 127.0.0.1:8379, please check the connection details." error message Expected behavior(A sh...
Where is RedisInsight installed, and how is it connecting to ElastiCache? Is the tunnelling setup so that redis traffic is proxied via an EC2 (or sorts) to the ElastiCache? — This is because the ElastiCache is in a private network and only application in the same VPC can access it. I...
Database zero (0) is not used, to prevent a conflict in AWS ElastiCache which inserts a special ElastiCacheMasterReplicationTimestamp key in the default database (at zero index) to aid replication. The Redis cluster topology is not supported because it cannot handle logical databases. Set the...
Actual behavior I see a "Could not connect to 127.0.0.1:6370, please check the connection details." error message Expected behavior Connection should be successful Screenshots Additional context OS: Ubuntu 22 Redis server: AWS Elasticache Redis 7.1 Redis Insight: v2.48 Redis CLI: v6.0.16Collabora...
Hello, I'm using SpringBoot 2.4.6 with Lettuce 6.0.5.RELEASE, and connecting to AWS Elasticache for Redis 6.X with one node and one read replica. Current Behavior For some reason, I'm not able to use RESP3 protocol (default), and I get a...
Well I don't believe my redis version matters, hence why I left it out. Each of our environments use something different - but once we upgraded from 2.0.601 to 2.1.30 - they ALL lost ability to connect via the application. But to answer your question, for local development I am using...