Using Jedis Client in Aws Lambda

Question

I have an Aws Lambda function which is in VPC, and also an Aws Redis Elasticache which is also in same VPC. I would like to put data to this cache by using Jedis Java client in my Aws Lambda Function, code is like below,

Jedis jedis = new Jedis("cache_url",6379);
jedis.set("testkey", "testvalue");

However, when i try to call this code block, i got an exception connect timeout

My Aws Lambda function is triggered by an Aws IOT Rule very frequently. What can cause this error?, or How can i use Jedis at my Aws Lambda function appropriately.

does your elasticache, have port 6379 opened, do check the inbound rules — Yogesh_D, Feb 17 '17 at 12:37
Thank you, Cache's security group configuration's inbound rule is closed, when i configure security group allowing 6379. It works correctly. — Arda Güçlü, Feb 17 '17 at 12:40
let me just add that as an answer so that anyone else stumbling here figures it out as well... — Yogesh_D, Feb 17 '17 at 12:58

score 1 · Accepted Answer · answered Feb 17 '17 at 12:58

1

The Connection Timeout would typically mean that the Lambda is not able to talk to you Elasticache. Check the security group on the Elasticache and make sure that it has Inbound rule to allow TCP connections on 6379.

answered Feb 17 '17 at 12:58

Yogesh_D

17,656
10
41
55

Using Jedis Client in Aws Lambda

1 Answers1