> ## 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.

# Move ElastiCache Node to Graviton

> Move ElastiCache nodes to the same-size Graviton node type, which costs less per hour.

Graviton ElastiCache nodes (m6g, m7g, r6g, r7g and t4g) list at a lower hourly price than the matching Intel nodes. nOps finds on-demand nodes on m5, m6i, m7i, r5, r6i, r7i and t3 and estimates the saving from moving each to the cheapest same-size Graviton node in the same region.

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

## Why it matters

The engine, size and data stay the same, so it is a price cut with no change for your application.

## How nOps finds it

nOps reads the last 7 days of on-demand ElastiCache node billing. m-family nodes are compared with m6g and m7g, r-family with r6g and r7g, and t3 with t4g, 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

An engine version that supports Graviton nodes. Permission to modify the cluster.

## How to implement

1. Check that your engine and version support the target node type.
2. 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`).
3. Make the change in a quiet period and watch memory and evictions afterwards.
4. 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.
* Reserved nodes bought for the Intel type do not cover the Graviton type.
* To roll back, modify the node type back.

## FAQs

> [accordion] Do I need to change my application?
>
> No. The cache engine and protocol are the same on Graviton.

## Related

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