CODEWITHSUNDEEP
redissails.jsamazon-elasticache
carpiediem
carpiediem

Reputation: 2038

Using AWS Elasticache Redis to manage sessions in Sails.js

I'm currently using connect-redis in my Sails.js project to leverage a locally-installed redis instance. In the future, I'd like to use a common redis instance for multiple server instances (behind a load balancer), so I've been looking at AWS Elasticache. I'm having trouble with the configuration, though.

sails-project\config\session.js:

adapter: 'connect-redis',
host: 'primary-endpoint.xxxxxx.ng.0001.apse1.cache.amazonaws.com',
port: 6379,
ttl: <redis session TTL in seconds>,
db: 0,
pass: <redis auth password>,
prefix: 'sess:',

What should the TTL value be? Should the pass attribute point to IAM somehow?

I tried creating a user in IAM with AmazonElastiCacheFullAccess permissions and putting its access key ID in the pass attribute, but I got this error in my server console (testing on my Windows box):

C:\repos\sails-project\node_modules\connect-redis\lib\connect-redis.js:83
      throw err;
      ^
AbortError: Redis connection lost and command aborted. It might have been processed.
    at RedisClient.flush_and_error (C:\repos\sails-project\node_modules\redis\index.js:362:23)
...

Any ideas on what to change?

Upvotes: 2

Views: 544

Answers (1)

d1ll1nger
d1ll1nger

Reputation: 1701

I'm going to assume your "windows box" is outside of AWS.

For Elasticache you can't access it from outside AWS. See the Security Section here : https://aws.amazon.com/elasticache/faqs/#Can_I_access_Amazon_ElastiCache_from_outside_AWS

The most common use case is to have EC2 instances within a VPC access and consume the Elasticache service. Along with this the Elasticache Redis service doesn't employ authentication and only allows lock down via security groups.

If you need something that differentiates from this configuration then you should look at putting Redis on EC2 so that you have full control.

Upvotes: 2

Related Questions