- Mais recentes
- Mais votos
- Mais comentários
Hello Joe.
If your EC2 is in a different subnet you should check routes and network ACL between Redis and Linux subnets, refer to this article about subnet routing.
Hope this helps.
Hi Joe,
In case this still isn't working for you please try the following:
- Check that your redis cluster has a security group added to it.
Go to ElastiCache -> Redis Clusters then select your cluster. Under "Network & Security" -> Security Groups check that there is a security group defined. If not, add a security group that allows connectivity from your EC2 instance and re-test.
- If your redis cluster already has a security group defined, check that it has an inbound rule which lets your EC2 instance connect to it.
Go to ElastiCache -> Redis Clusters then select your cluster. Under "Network & Security" -> Security Groups, select the security group to show the details of the inbound rules. Make sure there is an inbound rule for port 6379 coming from the security group of your EC2 instance (assuming you left the port number at the default)
Hopefully this will let you connect from your EC2 instance to the redis cluster using something like:
telnet <my-redis-endpoint> 6379
Same issue with mine , if you solve the issue, can you Let me Know how you can do that.
I'm able to connect with that but when i send the ping to the redis i got this response from that.
Error: Server closed the connection (5.01s)
You can check this in img also, try to help me how can i resolve that.
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 meses