-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Support at-rest and in-transit encryption for aws_elasticache_cluster (Redis) #4973
Comments
related #4105 |
Looks like |
@saravanan30erd appears to be correct here -- this feature is not available with the Elasticache has some confusing terminology when it comes to "clusters", where a Redis "cluster" (cluster mode enabled or disabled) is actually a "replication group" in terms of the API (and subsequently Terraform since it follows to the API implementation). You can create encrypted Redis replication groups (cluster mode enabled or disabled) via the Since there's nothing to implement here until AWS adds encryption support for individual Redis nodes (annoyingly "clusters" in the API) or Memcached clusters, we'll close this issue out until that changes. |
@bflad can we please reopen? Encryption in-transit and at-rest is now available both in create-cache-cluster and create-replication-group in AWS API. |
Yes, we badly need this to improve the security of our redis cache cluster |
Yep.. This feature is most essential |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
ElastiCache Redis version 4.0+ supports encryption at-rest and in-transit, also for non-clustered mode.
The terraform
aws_elasticache_cluster
currently does not support these features.New or Affected Resource(s)
Potential Terraform Configuration
Similar to how this is implemented in
aws_elasticache_replication_group
:References
The text was updated successfully, but these errors were encountered: