From d95ff6a081702d421a99aff62c4b53ee54414814 Mon Sep 17 00:00:00 2001 From: Saurabh Sharma Date: Wed, 15 May 2024 13:46:14 +0530 Subject: [PATCH] fix(docs): image not showing in aws-elasticache.md --- docs/gitbook/guide/redis-tm-hosting/aws-elasticache.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/gitbook/guide/redis-tm-hosting/aws-elasticache.md b/docs/gitbook/guide/redis-tm-hosting/aws-elasticache.md index f9efbfc71e..7d13d2496d 100644 --- a/docs/gitbook/guide/redis-tm-hosting/aws-elasticache.md +++ b/docs/gitbook/guide/redis-tm-hosting/aws-elasticache.md @@ -6,9 +6,8 @@ Here are some points to consider when using Elasticache with BullMQ within AWS: 1. Use the standard cache-nodes setup (i.e. not the serverless version, as serverless for the moment uses an incompatible maxmemory-policy) 2. In order to access your Elasticache instance you will need to create a security group that allows the instance to be accessible to the services running BullMQ instances. -3. - -
+3. +
4. You will need to specify a VPC and an Inboud rule. Most likely just a custom TCP with port range 6379 and some suitable source (anywhere works well for testing and in some simpler cases), remember that the cluster will not be accessible outside from AWS in any case. 5. Attach the security group to your Elasticache cluster and to the services that need to access it. 6. Make sure that you are using maxmemory-policy: noeviction in your Redis parameters. As you cannot modify any default parameter group you will need to create a new one.