> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrade ElastiCache Redis OSS to Valkey

> Upgrade ElastiCache Redis OSS clusters to Valkey on the same node type, at a lower hourly price.

Valkey is an open-source engine that is compatible with Redis OSS 7.2, and ElastiCache lists it at a lower hourly price than Redis OSS on the same node type. nOps finds on-demand Redis OSS nodes and estimates the saving from upgrading them to Valkey without changing the node type.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Database |
| **Service** | Amazon ElastiCache |
| **Action** | Modify |
| **Effort** | Medium |
| **Restart needed** | Yes |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

Applications keep working with the same commands and client libraries, so it is a price cut that needs no redesign and no change of instance size.

## How nOps finds it

nOps looks at the last 7 days of ElastiCache billing for nodes running Redis OSS on demand. For each node it compares the public list price of the node type on Redis OSS with the same node type on Valkey in the same region, and applies that difference to what the node actually cost. Nodes mostly covered by reserved nodes or credits, nodes that stopped running in the last few days, and savings under \$5 a month are left out.

## Before you start

Confirm your Redis OSS version and any modules or commands your application uses are supported by Valkey.

## How to implement

1. Check that your clients and any Redis modules work with Valkey, ideally on a test cluster first.
2. In the ElastiCache console, select the cluster and choose **Modify**, then change the engine to **Valkey** (or use `aws elasticache modify-replication-group --engine valkey`).
3. Apply the change in a maintenance window. ElastiCache upgrades the nodes in place on the same node type.
4. Update the engine in Terraform or CloudFormation so a later deployment does not switch it back.

## Risks and considerations

* The upgrade restarts the nodes. Use a maintenance window, and multi-AZ with replicas, to keep the cluster available.
* Existing ElastiCache reserved nodes keep applying after the switch to Valkey, at the Valkey price.

## FAQs

> [accordion] Do I need to change my application?
>
> Usually not. Valkey is compatible with Redis OSS 7.2 commands and clients. Check any Redis modules you use.

## Related

* [Move ElastiCache Node to Graviton](https://help.nops.io/inform/supported-recommendations/move-elasticache-node-to-graviton)
* [Move ElastiCache Node to Current Generation](https://help.nops.io/inform/supported-recommendations/move-elasticache-node-to-current-generation)
* [Upgrade MemoryDB from Redis OSS to Valkey](https://help.nops.io/inform/supported-recommendations/upgrade-memorydb-from-redis-oss-to-valkey)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.