- Newest
- Most votes
- Most comments
connection timeout means a connectivity issue. You need to make sure that NACL and Security Group allows ECS to connect to the Redis. In case when your Redis and ECS are in different VPCs, you also need to configure a peering and routing between them.
ecs security group is added in inbound rule of redis security group, but still same issue is persiting, am i writing code wrong way?
This is my code on node.js;
var redis = require("redis"); ////const redis = require('redis'); // const client = redis.createClient({ // host:'redis endpoint url', // port:6379, // }); // client.on("error", function (error) { // console.error("Error encountered:", error); // }); // client.on("connect", function (data1) { // console.log("Redis Connection Established"); // })
error : errno: 'ENOTFOUND',
Relevant content
asked 2 years ago- asked 6 months ago
- asked 19 days ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
Are you using route 53 at any point in the setup? I ran into similar issues in the past where my ECS containers were using only the private hosted zone of my domain. So I had to duplicate my public records into my private zone and that resolved it.
Can you update your post with code, which shows the way that you are connecting to redis?
This is my code on node.js;
var redis = require("redis"); ////const redis = require('redis'); // const client = redis.createClient({ // host:'redis endpoint url', // port:6379, // }); // client.on("error", function (error) { // console.error("Error encountered:", error); // }); // client.on("connect", function (data1) { // console.log("Redis Connection Established"); // })
errors: Error : Error: Redis connection in broken state: connection timeout exceeded.