Lambda Elasticache redis connection refused

Question

I'm trying to connect to Elasticache redis instance from lambda. Lambda and Elasticache are on same vpc and Lambda's execution role has all the permission for elasticache. But still I'm getting ECONNREFUSED.

const redis = require("redis");
const AWS = require("aws-sdk");
const apig = new AWS.ApiGatewayManagementApi({
  endpoint: process.env.ApiGatewayEndpoint,
});

exports.handler = async (event, context) => {
  const redisClient = redis.createClient({
    host: "botgo-cache.fhvwf2.ng.0001.aps1.cache.amazonaws.com",
    port: "6379",
  });
  
  await redisClient.connect();
  

  redisClient.on("connect", (err) => {
    console.log("Redis Connected " + err);
  });

  redisClient.on("error", (err) => {
    console.log("Redis Error " + err);
  });

  const TEST_KEY = "test_node";

  await redisClient.json.set(TEST_KEY, ".", { node: 4303 });
  const value = await redisClient.json.get(TEST_KEY, {
    // JSON Path: .node = the element called 'node' at root level.
    path: ".node",
  });

  console.log(`value of node: ${value}`);
};

Pranav · Accepted Answer · 2022-10-20 06:32:31Z

6

I was able to replicate your issue on my end. Do this:

const redisClient = redis.createClient({
    url: "rediss://botgo-cache.fhvwf2.ng.0001.aps1.cache.amazonaws.com:6379"
  });

This should fix it! And the rediss with double ss is important

Hope this helps!

answered Oct 20, 2022 at 6:32

Pranav

2463 silver badges8 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

jhilden Over a year ago

Thank you! I fought with this for a full day, so dumb.

PTucky Eagle Over a year ago

Great it solve my problem

Kendi Paet · Accepted Answer · 2022-06-09 12:24:06Z

1

Have you added security group to your Elasticache Redis cluster to allow incoming traffic to port 6379?

answered Jun 9, 2022 at 12:24

Kendi Paet

111 bronze badge

1 Comment

Haris Bouchlis Over a year ago

Not an answer, please delete and add it as a comment

Kellan · Accepted Answer · 2024-08-29 17:52:51Z

1

Your Redis cache instance, EC2 instance if you have one, and Lambda all need to share the same security groups and subnets.

Also, in your security group, make sure you have an inbound rule set up with Custom TCP and port 6379.

answered Aug 29, 2024 at 17:52

Kellan

193 bronze badges

Collectives™ on Stack Overflow

Lambda Elasticache redis connection refused

3 Answers 3

2 Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related