Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IT-3184] Fix nextflow Elasticache setup #251

Merged
merged 1 commit into from
Oct 18, 2023

Conversation

zaro0508
Copy link
Contributor

Fixed the following failures..

  • ElasticacheCluster AWS::ElastiCache::CacheCluster CREATE_FAILED Encryption feature is not supported for engine REDIS.
  • nextflow-elasticache-cluster AWS::CloudFormation::Stack ROLLBACK_IN_PROGRESS Template error: The ConfigurationEndpoint.Port attribute type is not supported for the redis cache cluster engine.
  • nextflow-elasticache-cluster AWS::CloudFormation::Stack ROLLBACK_IN_PROGRESS Template error: The ConfigurationEndpoint.Address attribute type is not supported for the redis cache cluster engine.

I was not able to enable transit encryption for Elasticache with Redis. The AWS docs[1] says it supported but I keep getting errors on multiple attempts. We just leave it unencrypted for now to get things working. We will attempt to encrypt later on. I do know that encryption is only supported on r6g instances and not r6gd instances so we are gonna switch to use the more common instance.

[1] https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/in-transit-encryption.html

Fixed the following failures..

* ElasticacheCluster AWS::ElastiCache::CacheCluster CREATE_FAILED Encryption feature is not supported for engine REDIS.
* nextflow-elasticache-cluster AWS::CloudFormation::Stack ROLLBACK_IN_PROGRESS Template error: The
  ConfigurationEndpoint.Port attribute type is not supported for the redis cache cluster engine.
* nextflow-elasticache-cluster AWS::CloudFormation::Stack ROLLBACK_IN_PROGRESS Template error: The
  ConfigurationEndpoint.Address attribute type is not supported for the redis cache cluster engine.

I was not able to enable transit encryption for Elasticache with Redis.
The AWS docs[1] says it supported but I keep getting errors on multiple
attempts.  We just leave it unencrypted for now to get things working.
We will attempt to encrypt later on.  I do know that encryption is only
supported on r6g instances and not r6gd instances so we are gonna switch
to use the more common instance.

[1] https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/in-transit-encryption.html
@zaro0508 zaro0508 requested a review from a team as a code owner October 18, 2023 18:39
@zaro0508 zaro0508 requested review from ConsoleCatzirl and a team and removed request for a team October 18, 2023 18:39
@thomasyu888 thomasyu888 merged commit 8dffb99 into Sage-Bionetworks-Workflows:dev Oct 18, 2023
5 checks passed
@zaro0508 zaro0508 changed the title Fix nextflow Elasticache setup [IT-3184] Fix nextflow Elasticache setup Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants