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

# Upgrade EC2 Auto Scaling Group

> Move an EC2 Auto Scaling group to a newer instance generation that costs less.

Newer EC2 instance generations usually cost the same or less than older ones and perform better. AWS Compute Optimizer recommends moving Auto Scaling groups on older generations to a current-generation type. nOps shows these recommendations with AWS's estimated monthly saving.

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

## Why it matters

The saving applies to every instance the group runs, and a launch template change rolls it out without touching each instance by hand.

## 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 recommends a newer-generation 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). An AMI with current ENA and NVMe drivers.

## How to implement

1. Check the AMI in the launch template supports the newer generation.
2. Create a new launch template version with the recommended instance type.
3. Point the group at the new version and start an instance refresh (`aws autoscaling start-instance-refresh`).
4. Watch health checks and application metrics during the refresh.
5. Update the launch template in Terraform or CloudFormation.

## Risks and considerations

* Older AMIs without ENA or NVMe drivers may fail to boot on newer generations.
* Reserved Instances bought for the old family may not cover the new one.
* To roll back, point the group at the previous launch template version and refresh again.

## Related

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