3 Answers
- Newest
- Most votes
- Most comments
0
Hi,
I have seen such a problem in the past, it got fixed by activating tls.
Corresponding js code:
let redisClient : RedisClientType = createClient({
socket: {hostname: 'myhost', port: 6379, tls: true}
});
Best,
Didier
0
Hello.
Will I be able to connect if I change the ElastiCache security group to allow all communications such as 0.0.0.0/0 to check the connection?
For example, if communication is possible with this setting, it is a problem with the inbound rules of ElastiCache's security group.
0
Not sure I understand the question, but I tested trying to allow connection to the elastiCache from anywhere just to see if it would work by allowing inbound traffic from anywhere. I couldn't make it work with the most relaxed rules.
answered 3 months ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 5 months ago
Thank you that was it. How silly. :(
Hi, you know: it happens to everybody (me included ;-) ). Anyway, glad that you found your problem. Thanks for accepting my answer.