How do I upgrade my self-managed ElastiCache for Redis OSS cluster to an ElastiCache for Valkey cluster?

Resolution

Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.

To avoid downtime and have a successful upgrade or migration, follow these best practices:

• Before you migrate your cluster, create a backup to include your latest content.
• For online migrations, it's a best practice to create 1 replica node for each shard. Replicas for ElastiCache for Redis OSS cluster allow you to complete the online migration with minimal disruption.
• Follow the upgrade considerations when working with self-designed clusters.
• Before you migrate to a production environment, it's a best practice to test your migration in a non-production environment.

To upgrade or migrate your cluster from an ElastiCache for Redis OSS cluster to an ElastiCache for Valkey cluster, use either the online or offline method.

Online method

To upgrade your engine or modify your cluster online, use one of the following methods:

• ElastiCache console
• AWS CLI
• ElastiCache API

Offline method

To upgrade your engine or modify your cluster offline, use an ElastiCache for Redis OSS cluster backup to recreate the cluster with the upgraded engine.

Complete the following steps:

1. Create a backup from the cluster.
2. Restore from the backup as a new cache. Or, export the cluster backup to a different AWS Region.
   Note: ElastiCache saves the backup as an rdb.file.
3. Create a new cache. For Creation method, choose Restore from backup and provide the Amazon Simple Storage Service (Amazon S3) file location.
4. After the cluster becomes available, replace the client endpoint with new endpoint from the Valkey cluster.

Related information

Get started with Amazon ElastiCache for Valkey

Amazon ElastiCache FAQs

How do I migrate my ElastiCache for Redis self-designed cluster within a Region, cross Region, or to a different account?

How do I minimize downtime when my ElastiCache for Redis is scaling?