Redis 6.2 will reach End of Life (EOL) on April 1, 2027 for Redis Cloud deployments. After this date, Redis 6.2 will no longer receive bug fixes, security updates, or support.
If you have databases running Redis 6.2, plan to upgrade ahead of the EOL date to remain on a supported version and retain full Redis support coverage.
If databases are not upgraded before April 1, 2027, Redis Cloud will automatically upgrade any remaining Redis 6.2 databases during scheduled maintenance windows. If a maintenance exclusion is in place, a documented justification is required to delay the upgrade.
Planning Before You Upgrade
Redis version upgrades can introduce breaking changes, though Redis minimizes them whenever possible. Any required breaking changes are introduced only in new major versions. Moving from Redis 6.2 to newer major versions may affect command behavior, client compatibility, module usage, or operational characteristics.
Before upgrading any production database:
-
Test in non-production first.
Validate application behavior against the target Redis version in staging or pre-production.
-
Review release notes and breaking changes.
Carefully qualify known changes for the target version using the Redis version release notes.
-
Select a target version deliberately.
Preferably the latest available version and review compatibility requirements and future upgrade paths before upgrading.
-
Plan rollback and maintenance timing.
Even supported upgrades may include brief failovers depending on topology and configuration.
If you're unsure about version selection, compatibility, or upgrade sequencing, involve Redis early to avoid outages.
Upgrade Options by Deployment Type
| Deployment Type | Upgrade Method / Instructions / Important Notes |
|---|---|
| Redis Cloud Pro (single-region) |
Upgrade Method: Self-serve (UI, API, Terraform) Instructions: In the Redis Cloud Console, select your database → More actions → Version upgrade. Follow the steps in the Redis Cloud database version upgrade documentation. Terraform users should update the Redis version in their configuration and apply changes using the Redis Cloud Terraform provider. Important Notes: Upgrades are performed per database and are customer-initiated, taking effect immediately when triggered. Test the target version in non-production first and review breaking changes before upgrading production. |
| Pro Active-Active (multi-region) |
Upgrade Method: Redis-assisted Instructions: In the Redis Cloud Console, go to Subscription → Request upgrade. Redis coordinates and performs the upgrade during a scheduled maintenance window. The request applies to all databases in the subscription. Important Notes: Upgrades are automatically scheduled during the subscription’s maintenance window, up to three weeks after the request was submitted. Target version selection and pre-production validation are strongly recommended. |
| Mixed subscriptions |
Upgrade Method: Combination of methods Instructions: Use self-serve upgrades for single-region or DREC databases. Submit a Request upgrade for Active-Active databases. Important Notes: Redis coordinates upgrades to minimize downtime and maintain version consistency. Ensure all environments are validated before production upgrades. |
If you are unsure how to proceed or need help selecting a target version:
Customers with an assigned Technical Account Manager should contact their TAM to build an upgrade plan.
Customers without an assigned TAM should open a Redis Support ticket to request assistance. A Redis support engineer can help assess upgrade readiness and sequencing.
Why upgrade
Upgrading before Redis 6.2 reaches EOL helps maintain security, stability, and full support coverage.
Newer Redis versions provide:
Improved performance and operational resilience
Advanced upgrade and scaling capabilities, including flexible shards (introduced in Redis 8)
Access to new features and modules
Ongoing patches and security updates
Automatic upgrades
If databases are not upgraded before April 1, 2027, Redis Cloud will automatically upgrade them to a supported version during maintenance windows.
Automatic upgrades ensure platform stability, continued compliance, and access to the latest supported Redis releases, but they do not replace the need for pre-production testing and upgrade planning.
Support and assistance
If you need help planning or performing your upgrade:
Access your account via Redis Cloud Console
Contact Redis Support for guidance with upgrade scheduling or complex environments
Related resources
0 comments
Please sign in to leave a comment.