MemoryDB Migrate To Valkey

Opportunity Name:

MemoryDB Migrate To Valkey

AWS Resource Type:

Amazon MemoryDB

Opportunity Description:

Amazon MemoryDB supports both the Redis engine and Valkey, an open-source, byte-for-byte compatible engine that AWS prices lower per node-hour. This opportunity identifies MemoryDB clusters running Redis that are eligible for an in-place engine migration to Valkey, and quantifies the annual saving from the Redis-to-Valkey price difference for your specific node type.

Criteria for identifying the opportunity:

• The cluster is currently running the Redis engine.
• The cluster's Redis engine version is 6.2 or later — this is the minimum version AWS supports for an in-place migration to Valkey 7.2.
• The cluster is not a member of a MemoryDB Multi-Region cluster (Multi-Region membership is excluded from this recommendation).

Potential savings (range in % on annual basis):

• The full Redis-to-Valkey per-node-hour price difference for your cluster's specific node type, projected annually. The exact percentage varies by node type and Region.

Can CloudFix implement the fix automatically once I accept the recommendation?

No, not yet. This is currently a finder-only recommendation; an automated fixer for the engine switch is planned as a follow-on. For now, the migration is performed manually from the MemoryDB console or API.

Other considerations:

• MemoryDB is a durable, persistent database, and the in-place engine migration is one-way — there is no supported downgrade path from Valkey back to Redis. Take a snapshot of your cluster before converting, as a precaution.
• Because Valkey is byte-for-byte protocol-compatible with Redis, your application code and client libraries do not need to change.
• This recommendation is specific to Redis-engine clusters. If you are running Redis on a cluster that is part of a Multi-Region setup, it will not appear here.

Additional Resources:

• Amazon MemoryDB for Valkey
• Supported Engine Versions