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

# Migrate EC2 Auto Scaling Group to Graviton

> Move the instances in an EC2 Auto Scaling group to lower-cost Graviton (Arm) instance types.

AWS Graviton instances use Arm processors and are priced lower than comparable x86 instances. AWS Compute Optimizer checks whether the workload in an Auto Scaling group is likely to run on Arm and recommends a Graviton instance type that fits its CPU and memory use. nOps shows these recommendations with AWS's estimated monthly saving.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Compute |
| **Service** | Amazon EC2 Auto Scaling |
| **Action** | Migrate to Graviton |
| **Effort** | Very high |
| **Restart needed** | Yes |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 14 days |
| **Source** | AWS Compute Optimizer |

## Why it matters

Auto Scaling groups often run many identical instances, so a cheaper instance type is multiplied across the whole group. A launch template change and an instance refresh roll it out without touching each instance.

## How nOps finds it

This recommendation comes from AWS Compute Optimizer, not from nOps. Compute Optimizer looks at the group's CloudWatch metrics over its lookback period and at the software it can identify, and recommends a Graviton type that still meets the workload's needs. nOps imports the recommendation daily from AWS Cost Optimization Hub, which returns one recommendation per resource (the one with the highest saving), and shows AWS's estimated monthly saving, which already takes your discounts into account.

## Before you start

AWS Compute Optimizer and AWS Cost Optimization Hub enabled for the account (or the whole organization). Software and container images that run on Arm64 (arm64 builds of your application, agents and libraries).

## How to implement

1. Confirm your application, AMI, agents and dependencies have Arm64 builds, and test them on a Graviton instance.
2. Create a new launch template version with an Arm64 AMI and the recommended Graviton instance type.
3. Point the Auto Scaling group at the new version and start an instance refresh (**EC2 → Auto Scaling groups → Instance refresh**, or `aws autoscaling start-instance-refresh`) so instances are replaced gradually.
4. Watch health checks and application metrics during the refresh.
5. Update the launch template in Terraform or CloudFormation.

## Risks and considerations

* Software built only for x86 will not start on Graviton. Test every component, including monitoring and security agents.
* Reserved Instances or EC2 Instance Savings Plans bought for the x86 family do not cover the new family.
* To roll back, point the group back at the previous launch template version and refresh again.

## FAQs

> [accordion] Do I have to rebuild my application?
>
> Interpreted languages (Python, Node.js, Java) usually run unchanged. Compiled code and container images need Arm64 builds.

## Related

* [Migrate EC2 Instance to Graviton](https://help.nops.io/inform/supported-recommendations/migrate-ec2-instance-to-graviton)
* [Rightsize EC2 Auto Scaling Group](https://help.nops.io/inform/supported-recommendations/rightsize-ec2-auto-scaling-group)
* [Upgrade EC2 Auto Scaling Group](https://help.nops.io/inform/supported-recommendations/upgrade-ec2-auto-scaling-group)
* [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.