[IT-3184] Setup Elasticache for nextflow #250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Per nextflow issue[1], Seqera suggest we use AWS elasticache with Redis instead of hosting redis in a docker container. This step is to setup Elasticache for nextflow. [1] https://support.seqera.io/support/tickets/4048
xschildw
approved these changes
Oct 17, 2023
ConsoleCatzirl
requested changes
Oct 17, 2023
ConsoleCatzirl
approved these changes
Oct 18, 2023
xschildw
approved these changes
Oct 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per nextflow issue[1], Seqera suggest we use AWS elasticache with Redis
instead of hosting redis in a docker container. This step is to
setup Elasticache for nextflow.
Note: once setup, we will need to configure nextflow'S TOWER_REDIS_URL[2]
parameter to use the AWS-generated endpoint. The backend and cron containers
need to be aware of this configuration in the environment section of the ECS template.
example:
[1] https://support.seqera.io/support/tickets/4048
[2] https://help.tower.nf/23.2/enterprise/configuration/overview/#tower-and-redis-databases:~:text=TOWER_REDIS_URL,redis%3A//redis%3A6379