connecting to AWS ElasticCache
See original GitHub issueHi, I’m moving resources from Azure to AWS and am having trouble connecting to Elasticache through ioredis.
Here’s my basic config:
const redisClient = new Redis({
port: process.env.REDIS_PORT,
host: process.env.REDIS_HOST
})
Here’s my Elasticache instance:
When trying to connect, it just times out. The strange thing is that if I use node-redis
with essentially the same config, it connects immediately.
Anything special that needs to be done?
Thx!
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Step 4: Connect to the cluster's node - Amazon ElastiCache ...
Connect to your Amazon EC2 instance using the connection utility of your choice. For instructions on how to connect to an Amazon EC2...
Read more >Connecting to nodes - Amazon ElastiCache for Redis
Connect to your Amazon EC2 instance using the connection utility of your choice. Note · To build redis-cli , download and install the...
Read more >Connecting to Elasticache - Amazon ... - AWS Documentation
The following examples use the Redis client to connect to ElastiCache. Topics. Connecting to a cluster mode disabled cluster; Connecting to a cluster...
Read more >Test connection to an ElastiCache Redit or Memcached Cluster
I want to test my connection to an Amazon ElastiCache for Redis or Amazon ElastiCache for Memcached cluster. How can I do this...
Read more >Step 4: Connect to the cluster's node - Amazon ElastiCache
Log in to an Amazon EC2 instance and connect to a node in the cache cluster.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Had the same “problem” yesterday, solved it by a coworker who had gone through the same problem some time ago. Posting my solution, maybe it helps out someone else.
You need to add
tls: {}
to the options, which is a bit counter-intuitive given the API docs and examples.Use
lazyConnect: true
and connect manually withawait redis.connect();