Description
Keeping an old Redis OSS version may leave needed fixes and security support unavailable. Choose a version consistent with the AWS ElastiCache support lifecycle and your patching requirements. A version alone does not establish compliance.
Potential impact
Responses to known issues may be delayed, and end-of-support or additional maintenance costs may affect the deployment.
Remediation
Move to a supported engine version and apply available updates. Test client and command compatibility first, and prepare backups and an outage plan. Configure encryption and access controls separately.
Examples
These examples compare an old 2.6.13 configuration with 7.1. For an actual migration, check the supported upgrade path and compatible node and parameter-group settings.
Before
hcl
resource "aws_elasticache_cluster" "redis_cluster" {
cluster_id = "cluster-example"
engine = "redis"
node_type = "cache.m4.large"
num_cache_nodes = 1
engine_version = "2.6.13"
port = 6379
}
After
hcl
resource "aws_elasticache_cluster" "redis_cluster" {
cluster_id = "cluster-example"
engine = "redis"
node_type = "cache.m4.large"
num_cache_nodes = 1
engine_version = "7.1"
port = 6379
}