// Redis EOL and ElastiCache extended support
Redis EOL: patched Redis 6 and 7 builds
instead of ElastiCache extended-support fees.
Redis EOL depends on the line: 7.0 ended on 29 July 2024, 6.2 ends on 1 April 2027, and 7.2 and 7.4 run to 1 December 2029, while Amazon ElastiCache bills extended support for Redis OSS 4 and 5 now and for version 6 from 1 February 2027. OSSeva ships signed, patched builds of Redis 6.2 and 7.0 that you run on your own servers or Kubernetes, supports Redis 7.2 and Valkey, and plans the move off ElastiCache when that is the cheaper route. Enter your work email and the Redis version you run, and an engineer replies within 1 business day.
- Patched builds
- Redis 6.2 and 7.0, signed, as apt and yum packages and container images
- Also supported
- Redis 7.2, Valkey 7.2 and Valkey 8.x
- Critical CVEs (CVSS 9.0 or higher)
- Patched within 48 hours
- High-severity CVEs
- Patched within 7 days
- Support hours
- Assure includes 24/7 reactive support; Operate adds a 15-minute P1 response
- Pricing model
- Per instance cluster, not per GB of memory or per operation
Dates checked on 20 October 2026 against redis.io (Redis Open Source version management), endoflife.date (redis and valkey) and the AWS ElastiCache User Guide.
Trusted globally by enterprises





Redis versions and end-of-life dates
Redis EOL differs by line. Redis 7.0 ended on 29 July 2024, 6.2 ends on 1 April 2027, 7.2 and 7.4 run to 1 December 2029, and 8.0 ends on 1 December 2026. Dates checked 20 October 2026 on redis.io and endoflife.date, which agree.
| Line | Released | Community end of life | Latest release | Licence | Status |
|---|---|---|---|---|---|
| Redis 8.2 | 4 Aug 2025 | 1 Sep 2030 | 8.2.10 | RSALv2, SSPLv1 or AGPLv3 | Supported upstream (extended release) |
| Redis 8.0 | 2 May 2025 | 1 Dec 2026 | 8.0.6 | RSALv2, SSPLv1 or AGPLv3 | Supported upstream until 1 Dec 2026 |
| Redis 7.4 | 29 Jul 2024 | 1 Dec 2029 | 7.4.12 | RSALv2 or SSPLv1 | Supported upstream (extended release) |
| Redis 7.2 | 15 Aug 2023 | 1 Dec 2029 | 7.2.17 | BSD-3-Clause | Supported upstream; OSSeva supports it |
| Redis 7.0 | 27 Apr 2022 | 29 Jul 2024 | 7.0.15 | BSD-3-Clause | Ended: OSSeva patched builds |
| Redis 6.2 | 22 Feb 2021 | 1 Apr 2027 | 6.2.24 | BSD-3-Clause | Upstream fixes until 1 Apr 2027; OSSeva patched builds, before and after |
| Redis 6.0 | 30 Apr 2020 | 31 May 2022 | 6.0.20 | BSD-3-Clause | Ended: move to 6.2 or Valkey |
| Redis 5.0 | 17 Oct 2018 | 27 Apr 2022 | 5.0.14 | BSD-3-Clause | Ended: move to 6.2 or Valkey |
Sources: redis.io (Redis Open Source version management) and endoflife.date/redis. Latest releases as of the check date. Redis 8.0 has had no release since 8.0.6 (22 February 2026).
What ElastiCache extended support changes
Amazon ElastiCache keeps old Redis OSS versions running past the end of standard support and bills for it. The charge is a premium on the on-demand node price for every node still on the old version, it doubles in the third year, and reserved-node discounts do not apply to it. AWS applies Extended Support to the latest patch version of each major version only. Price it on your own node count at the AWS ElastiCache pricing page, then compare it with an OSSeva quote in the cost calculator.
| ElastiCache engine | End of standard support | Extended Support billing starts | Extended Support ends |
|---|---|---|---|
| Redis OSS v4 | 31 Jan 2026 | 1 Feb 2026 | 31 Jan 2029 |
| Redis OSS v5 | 31 Jan 2026 | 1 Feb 2026 | 31 Jan 2029 |
| Redis OSS v6 | 31 Jan 2027 | 1 Feb 2027 | 31 Jan 2030 |
| Redis OSS v7 | No end date announced | n/a | n/a |
Source: AWS ElastiCache User Guide, "Versions with ElastiCache Extended Support", checked 20 October 2026. Caches still on Redis OSS v4 or v5 when Extended Support ends are upgraded automatically to the latest Valkey.
ElastiCache Extended Support cost, explained →Support cost calculator →
Advisories published since Redis 7.0 ended
Redis 7.0 ended on 29 July 2024, and its last release was 7.0.15. The CVE directory lists six advisories published after that date that cover the 7.0 line and are scored 7.0 or higher, one of them scored 9.0 or higher. Upstream fixed each one in 6.2.x, 7.2.x and later lines. None has a 7.0 release. Redis 6.2 carries these fixes until it ends on 1 April 2027, and joins 7.0 after that.
| CVE | Published | CVSS | Affected range (NVD) | Fixed upstream in |
|---|---|---|---|---|
| CVE-2024-31449 | 2024-10-07 | 8.8 | 2.8.18 and later, before 6.2.16, 7.2.6 and 7.4.1 | 6.2.16, 7.2.6, 7.4.1 |
| CVE-2025-21605 | 2025-04-23 | 7.5 | 2.6 and later, before 6.2.18, 7.2.8 and 7.4.3 | 6.2.18, 7.2.8, 7.4.3 |
| CVE-2025-32023 | 2025-07-07 | 7.8 | 2.8 and later, before 6.2.19, 7.2.10, 7.4.5 and 8.0.3 | 6.2.19, 7.2.10, 7.4.5, 8.0.3 |
| CVE-2025-48367 | 2025-07-07 | 7.5 | All versions before 6.2.19, 7.2.10, 7.4.5 and 8.0.3 | 6.2.19, 7.2.10, 7.4.5, 8.0.3 |
| CVE-2025-46817 | 2025-10-03 | 8.8 | All versions with Lua scripting before 6.2.20, 7.2.11, 7.4.6, 8.0.4 and 8.2.2 | 6.2.20, 7.2.11, 7.4.6, 8.0.4, 8.2.2 |
| CVE-2025-49844 | 2025-10-03 | 9.9 | <6.2.20; >=7.0 <7.2.11; >=7.4.0 <7.4.6; >=8.0.0 <8.0.4 | See advisory |
The directory lists Redis CVEs matched at NVD to the product with a CVSS score of 7.0 or higher, so it is a subset of every Redis advisory. Affected ranges are as NVD publishes them.
Why Redis 6 and 7 estates stay where they are
Redis upgrades are usually easy technically. The reasons to wait are commercial, legal and contractual.
7.2 is the last BSD-licensed Redis
Redis 7.4 moved to RSALv2 or SSPLv1, and Redis 8 added AGPLv3. Organisations with an AGPL ban or a hosted product built on Redis often cannot take a newer Redis at all. Redis 7.2 stays supported upstream to 1 December 2029, which gives them room to plan the Valkey move instead of rushing it.
ElastiCache bills for versions it no longer supports as standard
AWS enrols caches still on Redis OSS 4 and 5 in Extended Support from 1 February 2026, and version 6 follows on 1 February 2027. The premium is added to the on-demand price of every node on that version and doubles in the third year. Upgrading inside ElastiCache to Valkey or a current Redis OSS version ends the charge, so the case for leaving ElastiCache is a licence, control or cost-structure case, not only a version case.
Valkey is a migration, not a patch
Valkey is protocol-compatible and usually straightforward, but it is still a change of engine that needs client and workload testing, and it is not always possible inside a managed service contract.
The dates that matter
2024-03-20
Redis announces the move from BSD to RSALv2 and SSPLv1 for future releases. 7.2 remains BSD.
2024-07-29
Redis 7.0 end of life. The last release was 7.0.15.
2025-05-01
Redis adds AGPLv3 as a licence option from Redis 8.
2026-02-01
ElastiCache Extended Support charges begin for Redis OSS 4 and 5.
2026-12-01
Redis 8.0 end of life. Redis 8.2 is the extended release, supported to 1 September 2030.
2027-02-01
ElastiCache Extended Support charges begin for Redis OSS 6.
2027-04-01
Redis 6.2 end of life.
2029-12-01
Redis 7.2 and 7.4 end of life.
What OSSeva delivers
Patched Redis 6.2 and 7.0
Backported security fixes for the Redis lines you run self-managed, built from upstream source and delivered as signed packages and images. Critical CVEs within 48 hours, High within 7 days.
ElastiCache exit
Your ElastiCache bill set against the cost of running the cluster yourself, with the support side priced per cluster. Then the cutover to self-managed Redis or Valkey where it makes sense.
Valkey migration
Compatibility checks, client testing and a staged move from Redis to Valkey, supported afterwards.
Move to Valkey or stay on Redis
Valkey is the Linux Foundation fork of Redis 7.2.4 and stays under BSD-3-Clause. It speaks the same protocol, so most clients connect unchanged. Stay on Redis 7.2 if the licence is not the constraint and the move to a new engine can wait; Redis 7.2 is supported upstream to 1 December 2029. Move to Valkey if you need a BSD licence after the 7.2 line or want one maintained line for the long term. OSSeva supports Valkey 7.2 and 8.x, plans the move with client and workload testing, and keeps the Redis 6.2 or 7.0 estate patched while you test.
If you run on ElastiCache and only want to stop the extended-support premium, the cheapest first step is usually an upgrade inside ElastiCache to Valkey or a supported Redis OSS version. OSSeva is the answer when the cache has to leave ElastiCache, when a BSD line has to hold until a Valkey test finishes, or when the cluster runs on your own infrastructure.
Valkey release lines (endoflife.date, checked 20 October 2026)
| Line | Released | Community end of life |
|---|---|---|
| Valkey 7.2 | 16 Apr 2024 | 16 Apr 2029 |
| Valkey 8.0 | 15 Sep 2024 | 15 Sep 2027 |
| Valkey 8.1 | 31 Mar 2025 | 31 Mar 2030 |
| Valkey 9.0 | 21 Oct 2025 | 21 Oct 2028 |
| Valkey 9.1 | 19 May 2026 | 19 May 2031 |
Patched Redis builds on your infrastructure
OSSeva builds Redis 6.2 and 7.0 from the upstream source and backports the fixes for advisories that upstream no longer fixes on those lines. Builds are signed and arrive as apt and yum packages and container images. Cluster, Sentinel and standalone modes, RDB and AOF formats and your configuration stay as they are, so the swap is a package or image change.
Critical CVEs (CVSS 9.0 or higher) are patched within 48 hours and High within 7 days; everything else goes into a quarterly batch. Assure adds the compliance documentation and the SBOMs and CVE remediation records an auditor asks for, with 24/7 reactive support. Operate adds 24/7 monitoring, named engineers and a 15-minute P1 response.
OSSeva for Redis is priced per instance cluster, so adding memory or throughput does not change the support bill. Book a discovery call for a quote, then put it in the support cost calculator next to what you pay today.
Which vendors patch Redis 7.0 and 6.2 after community support ends?
| Option | What you get | Trade-off |
|---|---|---|
| Upgrade inside ElastiCache | ElastiCache for Valkey or a Redis OSS version in standard support; the premium stops when the cache leaves the old version | A major-version upgrade tested against your clients, and a Valkey or newer Redis engine inside the same AWS contract. |
| Stay on ElastiCache Extended Support | Patched old versions inside AWS, with no migration | A premium on every node that doubles in year three, applied to the latest patch version of the major only. |
| Move to Valkey | A BSD-licensed, maintained engine | An engine change that needs testing. |
| Move to Redis 8 | The current Redis | RSALv2, SSPLv1 or AGPLv3 licence terms, and 8.0 ends on 1 December 2026. |
| OSSeva extended support | Patched self-managed Redis 6.2 and 7.0, and support for 7.2 and Valkey | Self-managed operation, which OSSeva can take on. |
Redis dates and licences from redis.io (Redis Open Source version management, the 2024 licensing announcement and the AGPLv3 announcement) and endoflife.date. ElastiCache dates and the premium structure from the AWS ElastiCache User Guide and pricing page. Checked 20 October 2026.
When is Redis end of life?
It depends on the line. Redis 7.0 ended on 29 July 2024, 6.2 ends on 1 April 2027, 8.0 ends on 1 December 2026, and 7.2 and 7.4 run to 1 December 2029. Redis 8.2 is supported to 1 September 2030. Dates checked on redis.io and endoflife.date on 20 October 2026.
Is Redis 7 end of life?
Redis 7.0 is. It ended on 29 July 2024 at 7.0.15. Redis 7.2 and 7.4 are extended releases, supported upstream to 1 December 2029.
What does ElastiCache Extended Support cost?
AWS adds a premium to the on-demand price of every node still on an old Redis OSS version, for versions 4 and 5 from 1 February 2026 and version 6 from 1 February 2027. The premium doubles in the third year, and reserved-node discounts do not apply to it. AWS publishes the rates on its ElastiCache pricing page; take your own node count and region from there, then compare the result with an OSSeva quote, which is priced per cluster.
Is Redis still open source?
Redis 7.2 and earlier are BSD-3-Clause. Redis 7.4 moved to RSALv2 or SSPLv1 in March 2024, and Redis 8 added AGPLv3 as a third option in May 2025. AGPLv3 is an OSI-approved open source licence; RSALv2 and SSPLv1 are source-available. Valkey continues the BSD line from Redis 7.2.4.
Did Redis change its license?
Yes. Redis Ltd. announced on 20 March 2024 that future releases would be dual-licensed under RSALv2 and SSPLv1 instead of BSD-3-Clause. Versions released before the change, including 7.2 and the 6.x and 7.0 lines, stay under BSD-3-Clause. The Linux Foundation launched Valkey as a BSD fork in response.
Is Redis no longer free?
Redis Open Source remains free to download and run under RSALv2, SSPLv1 or, from Redis 8, AGPLv3. RSALv2 and SSPLv1 restrict offering Redis as a service to others, and AGPLv3 carries copyleft obligations, so check your use with your own counsel. Redis 7.2 and earlier, and Valkey, are BSD-3-Clause.
Which companies offer Redis support for self-managed clusters?
Redis Ltd. supports its own commercial products, Redis Software and Redis Cloud. Cloud providers support the managed services they run. OSSeva supports self-managed Redis OSS, including patched builds of 6.2 and 7.0 and support for 7.2, and supports Valkey.
How do I move from Redis to Valkey?
Check client compatibility, test your real workload against Valkey, then cut over in stages with a rollback path. OSSeva plans and supports the move and keeps the Redis estate patched while you test.
Get a quote
Stay on BSD Redis without the surcharge.
A 15-minute discovery call, your ElastiCache bill set against self-managed, and a proposal within five working days.
Prefer to talk or read more first?