> ## 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 MemoryDB from Redis OSS to Valkey

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

MemoryDB lists Valkey nodes at a lower hourly price than Redis OSS nodes of the same type. Valkey is an open-source engine compatible with Redis OSS, and MemoryDB can upgrade a cluster's engine in place. nOps finds on-demand Redis OSS clusters and estimates the saving from the node-hour price difference.

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

## Why it matters

It is a price cut that needs no change of node type or cluster size, and usually no application change.

## How nOps finds it

nOps reads the last 7 complete days of on-demand MemoryDB node billing on Redis OSS for each cluster. The saving is the node cost, scaled to a month, times the difference between the public Valkey and Redis OSS node-hour prices for the same node type and region. Data-written and snapshot charges are not counted. Clusters not running recently, clusters mostly on reserved nodes or credits and savings under \$5 a month are left out.

## Before you start

Confirm your client libraries and any Redis-specific features work with Valkey, ideally on a test cluster.

## How to implement

1. Test your application against a Valkey cluster first.
2. Upgrade the engine (MemoryDB console: **Clusters → your cluster → Modify → Engine → Valkey**, or `aws memorydb update-cluster --cluster-name CLUSTER --engine valkey --engine-version VERSION`).
3. Apply it in a maintenance window and watch the cluster afterwards.
4. Update the engine in Terraform or CloudFormation so a later deployment does not switch it back.

## Risks and considerations

* Plan the upgrade as one-way: switching a MemoryDB cluster back from Valkey to Redis OSS is not a simple in-place change.
* The upgrade replaces nodes one at a time; use a maintenance window.
* Existing reserved nodes keep applying after the switch.

## FAQs

> [accordion] Do I need to change my application?
>
> Usually not. Valkey uses the same commands and clients as Redis OSS. Test first.

## Related

* [Upgrade ElastiCache Redis OSS to Valkey](https://help.nops.io/inform/supported-recommendations/upgrade-elasticache-redis-oss-to-valkey)
* [Move ElastiCache Node to Current Generation](https://help.nops.io/inform/supported-recommendations/move-elasticache-node-to-current-generation)
* [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.