Why it matters
For workloads that already run on Arm-friendly software, moving to Graviton is one of the larger per-instance savings and needs no change in how the instance is used.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 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). An Arm64 AMI and Arm64 builds of your application and agents.How to implement
- Confirm your operating system, application, agents and libraries have Arm64 builds.
- Launch a test instance of the recommended Graviton type from an Arm64 AMI and run the workload on it.
- Move the workload: build a new instance from an Arm64 AMI (you cannot change an x86 instance to Graviton in place), move data and traffic to it, then terminate the old one.
- For instances in an Auto Scaling group, change the launch template instead.
- Update Terraform or CloudFormation with the new AMI and instance type.
Risks and considerations
- An x86 AMI cannot boot on Graviton, so this is a migration to a new instance, not a type change.
- Software built only for x86 will not run. Test everything, including monitoring and security agents.
- Reserved Instances or EC2 Instance Savings Plans bought for the x86 family do not cover the new family.
- Keep the old instance or its AMI until the new one is proven, so you can switch back.
FAQs
Can I just change the instance type?
Can I just change the instance type?
No. Graviton needs an Arm64 AMI, so you launch a new instance and move the workload to it.