Why it matters
Instances launched years ago often stay on their original generation. Moving to a current generation lowers the price and usually improves performance at the same time.How nOps finds it
This recommendation comes from AWS Compute Optimizer, not from nOps. Compute Optimizer looks at the instance’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). Current ENA and NVMe drivers in the AMI, which newer generations require.How to implement
- Check the AMI supports the newer generation (ENA networking and NVMe storage drivers).
- Stop the instance, change its instance type (Actions → Instance settings → Change instance type, or
aws ec2 modify-instance-attribute --instance-type), then start it. - For instances in an Auto Scaling group, change the launch template and run an instance refresh instead.
- Update Terraform or CloudFormation so a later deployment does not change it back.
Risks and considerations
- Changing the instance type needs a stop and start.
- Older AMIs without ENA or NVMe drivers may not boot on newer generations. Test first.
- Reserved Instances bought for the old family may not cover the new one.
- To roll back, stop the instance and change the type back.