Why it matters
Old node types are easy to forget in long-running caches. Moving keeps the same engine and size, so the cache behaves the same at a lower price.How nOps finds it
nOps reads the last 7 days of on-demand ElastiCache node billing. t2 nodes are compared with t3 and t4g, m3 and m4 with m5, m6g and m7g, and r3 and r4 with r5, r6g and r7g, all of the same size, at public list prices in the same region. The saving is the node’s on-demand cost, scaled to a month, times the list-price difference to the cheapest target. Nodes not running in the last 2 days, nodes mostly covered by reserved nodes or credits, and savings under $5 a month are left out.Before you start
Permission to modify the cluster (elasticache:ModifyReplicationGroup or elasticache:ModifyCacheCluster).
How to implement
- Check that your engine and version support the target node type.
- Change the node type (ElastiCache console: your cluster → Modify → Node type, or
aws elasticache modify-replication-group --replication-group-id GROUP --cache-node-type NEW_TYPE --apply-immediately). - Make the change in a quiet period and watch memory and evictions afterwards.
- Update the node type in Terraform or CloudFormation so a later deployment does not change it back.
Risks and considerations
- Changing the node type replaces the nodes. For Valkey and Redis OSS replication groups this is online; for Memcached it means a new cluster.
- Graviton targets (t4g, m6g, m7g, r6g, r7g) need an engine version that supports them.
- Reserved nodes bought for the old type do not cover the new one.
- To roll back, modify the node type back.
FAQs
Does the cache size change?
Does the cache size change?
No. nOps only compares node types of the same size.