12
votes

I am getting connection timeout from EC2 trying to connect to AWS Elasticache.

I launched a 1-node elasticache cluster I launched an EC2 instance, made sure availability zone was the same as the cluster, us-west-2b

I did not create a new VPC. I see one is already created.

I ran a nslookup on my elasticache endpoint. It looks like a different /20 than my ec2.

I looked through the documentation and the ec2 launch and did not see where I can specify the subnet, except the availabilty zone.

3
My elasticache IP is 172.31.36.xxx . In EC2, my only available subnets are 172.31.0.0/20, 172.31.16.0/20 and 172.31.32.0/20 ???stampede76
Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault.kaylum

3 Answers

13
votes

I think the problem is about security groups of your instance.

To the best of my knowledge you need to allow the traffic on the security group associated to your EC2 instance.

If you are using memcached the port is 11211 if redis the port is 6379

Try to have a look to the AWS official documentation.

http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/GettingStarted.AuthorizeAccess.html

I hope this helps somehow.

6
votes

Actually solution is to add security group to elasticache cluster, and this security group should allow 6379 port. enter image description here

5
votes

First, check the instance security group and check port 6379 is allowed in Inbound.

After that, check your default VPC security group and add inbound rule Custom TCP Rule-6379-Anywhere and save.

I hope this will fix the issue.