Version and Upgrade Strategy
Understand ElastiCache version and upgrade strategies to manage Redis OSS lifecycle risks and costs. Explore Valkey migration options, in-place and cross-engine upgrades, and combining cluster mode transitions. Learn how to plan upgrades to minimize disruptions, ensure compatibility, and maintain modern, secure caching infrastructure aligned with AWS best practices.
The previous lesson explored AI-era ElastiCache capabilities such as vector search on Valkey 8.2 node-based clusters, semantic caching, and agentic memory patterns. Those features represent the forward edge of what ElastiCache can deliver, but none of them are accessible to teams still running Redis OSS 4 or 5. The gap between modern capability and legacy engine versions is not just a feature gap. It is a life cycle risk that compounds over time.
ElastiCache engine versions follow a defined support life cycle. Each version moves through standard support, transitions into Extended Support, and eventually reaches an automatic upgrade deadline. Standard support for Redis OSS versions 4 and 5 ended on January 31, 2026, which means clusters running those versions are now accumulating additional cost and reduced patch coverage. Ignoring this timeline does not pause it. It simply converts a planned migration into an eventual emergency.
This lesson unpacks the key terms that govern this life cycle:
The following diagram illustrates how these life-cycle stages relate to each other and where Redis OSS 4 and 5 currently sit on the timeline.
Redis OSS life cycle and Extended Support
When a Redis OSS version exits standard support, AWS stops releasing regular security patches and bug fixes for that version under the standard model. The engine remains available, but the safety net shrinks.
What Extended Support actually provides
It is not a continuation of business as usual. The patching cadence drops, the per-node cost rises, and the clock continues ticking toward the automatic upgrade deadline.
Attention: The most...