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
- Check the AMI in the launch template supports the newer generation.
- Create a new launch template version with the recommended instance type.
- Point the group at the new version and start an instance refresh (
aws autoscaling start-instance-refresh). - Watch health checks and application metrics during the refresh.
- 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.