ElastiCache Migration to Valkey

Opportunity Name: ElastiCache Migration to Valkey

AWS Resource Type: Amazon ElastiCache (Redis OSS Clusters)

Opportunity Description:
This Finder identifies ElastiCache Redis OSS clusters that can be migrated to Valkey 7.2, a new open-source Redis-compatible engine. Valkey offers up to 20% lower pricing, improved multi-core utilization, asynchronous I/O threading, and reduced memory overhead—making it a cost-efficient, high-performance alternative. It is fully compatible with Redis OSS, meaning no application code changes are required for migration.

Criteria for identifying the opportunity:

• Cluster engine is Redis OSS.
• Cluster is active and not tagged with cloudfix_dont_fix_it.
• Estimated annualized cost of Redis cluster ≥ $100.
• Cluster is eligible for Valkey engine switch based on AWS compatibility.
• Pricing savings are calculated at ~20% of current node-based costs.

Potential Savings (range in % on annual basis):

• Estimated average customer savings: ~$6,000 per year.
• Larger enterprise accounts may see savings exceeding $100,000 annually.

What happens when the Fixer is executed?
CloudFix now includes an automated Fixer for this opportunity. The Fixer:

1. Uses the AWS modify-cache-cluster API to change the engine from Redis OSS to Valkey.
2. Applies new configuration tags to track the migration.
3. Executes pre-migration validation and post-migration verification steps.
4. Updates the engine in-place where possible, ensuring smooth transition.

AWS CLI command used:

aws elasticache modify-cache-cluster \
  --cache-cluster-id <cluster_id> \
  --engine valkey

Is it possible to rollback once CloudFix implements the fixer?
 No automated rollback is currently available. Manual reversion to Redis OSS would require cluster recreation or snapshot-based recovery. Customers are advised to validate test environments prior to migration.

Can CloudFix implement the fix automatically once I accept the recommendation?
 Yes. Once approved, CloudFix will automatically execute the migration runbook using AWS SDK and CLI operations.

Does this fix require downtime?
 Minimal or near-zero downtime is expected when AWS zero-downtime migration tools are used. However, testing in pre-production environments is strongly advised before live migration.

Additional Resources:

• Key Considerations in Moving to Valkey on ElastiCache and MemoryDB
• AWS modify-cache-cluster Documentation
• AWS ElastiCache Documentation