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
- Check that your clients and any Redis modules work with Valkey, ideally on a test cluster first.
- 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). - Apply the change in a maintenance window. ElastiCache upgrades the nodes in place on the same node type.
- 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
Do I need to change my application?
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.