EOL.WikiEOL.Wiki
← ← Back to all products

Amazon ElastiCache for Redis OSS

Active
OtherLatest Version: 7Latest Release: N/A

Support summary

Amazon ElastiCache for Redis OSS currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

Jan 31, 2027

Amazon ElastiCache for Redis OSS 6 · 221 days left

Supported cycles

2

0 lts

Versions

4

Latest Version

7

Active Support

2

EOL

2

Lifecycle Timeline

Today
7
7
6
6
5
5
4
4
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
7Apr 12, 2022YesNo7No
Active
6Oct 13, 2020YesJan 31, 20276No
Active
5Oct 17, 2018NoJan 31, 20265No
EOL
4Nov 17, 2017NoJan 31, 20264No
EOL

Data sources

Frequently Asked Questions

Which versions of Amazon ElastiCache for Redis OSS have reached end of life?
The following Amazon ElastiCache for Redis OSS versions have reached end of life and no longer receive security updates: 5, 4. It is recommended to upgrade to a supported version.
Is it safe to continue using Amazon ElastiCache for Redis OSS 5?
Amazon ElastiCache for Redis OSS 5 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Amazon ElastiCache for Redis OSS?
The latest version of Amazon ElastiCache for Redis OSS is 7, released in the 7 release cycle.
How many versions of Amazon ElastiCache for Redis OSS are currently supported?
Amazon ElastiCache for Redis OSS currently has 2 actively supported version(s): 7, 6.
When does Amazon ElastiCache for Redis OSS 7 reach end of life?
Amazon ElastiCache for Redis OSS 7 does not have a specific end-of-life date announced yet.
What should I do when Amazon ElastiCache for Redis OSS reaches end of life?
When a Amazon ElastiCache for Redis OSS version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.