> ## 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 OpenSearch Domain to Graviton

> Move OpenSearch domains to the same-size Graviton instance type, which costs less per hour.

Graviton OpenSearch instance types (m6g, m7g, r6g, r7g, c6g, c7g and t4g) list at a lower hourly price than the matching Intel and AMD types. nOps finds on-demand OpenSearch instances on x86 types and estimates the saving from moving each to the cheapest same-size Graviton type, per domain and instance type (data and dedicated master nodes are counted separately).

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

## Why it matters

OpenSearch clusters run around the clock, so a lower hourly price on every node adds up. The change keeps the same size and data.

## How nOps finds it

nOps reads the last 7 days of on-demand OpenSearch instance billing (UltraWarm is left out). m, r, c and t family instances are compared with m6g/m7g, r6g/r7g, c6g/c7g and t4g of the same size, at public list prices in the same region. The saving is the on-demand cost, scaled to a month, times the list-price difference to the cheapest target. Instances not running in the last 2 days, instances mostly covered by reserved instances or credits, and savings under \$5 a month are left out.

## Before you start

An OpenSearch or Elasticsearch version that supports Graviton instances. Enough free storage for a blue/green deployment. Permission to update the domain (`es:UpdateDomainConfig`).

## How to implement

1. Check that the domain's engine version supports the Graviton type.
2. Change the instance type (OpenSearch console: **Domains → your domain → Actions → Edit cluster configuration**, or `aws opensearch update-domain-config --domain-name DOMAIN --cluster-config InstanceType=NEW_TYPE.search`). Do the same for dedicated master nodes if they are listed.
3. OpenSearch runs a blue/green deployment. Wait until the domain is **Active** again before making other changes.
4. Update Terraform or CloudFormation so a later deployment does not change it back.

## Risks and considerations

* The blue/green deployment copies all data to new nodes, which adds load and can take hours on large domains. Run it in a quiet period.
* Reserved instances bought for the old type do not cover the Graviton type.
* To roll back, change the instance type back; this runs another blue/green deployment.

## FAQs

> [accordion] Is there downtime?
>
> No. OpenSearch keeps the domain available during the blue/green deployment, though it can be slower while data is copied.

## Related

* [Move ElastiCache Node to Graviton](https://help.nops.io/inform/supported-recommendations/move-elasticache-node-to-graviton)
* [Migrate EC2 Instance to Graviton](https://help.nops.io/inform/supported-recommendations/migrate-ec2-instance-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.