Why it matters
Instances often stay on the generation they were launched with for years, while newer generations give more for less.How nOps finds it
This recommendation comes from AWS Compute Optimizer through Cost Optimization Hub, not from an nOps rule. AWS looks at the instance over its lookback period (14 days by default) and recommends a newer-generation class that fits. The saving is AWS’s estimate, including your Reserved Instance and Savings Plans pricing.Before you start
AWS Compute Optimizer and Cost Optimization Hub enabled. The engine version must support the new class.How to implement
- Check that your engine version supports the recommended class.
- Change the class in a maintenance window (RDS console → Modify → DB instance class, or
aws rds modify-db-instance --db-instance-identifier DB_ID --db-instance-class NEW_CLASS). - For Aurora, change readers first and fail over, so the writer changes last.
- Update Terraform or CloudFormation so a later deployment does not change it back.
Risks and considerations
- Changing the class restarts the database. With Multi-AZ the outage is usually a short failover.
- Reserved Instances bought for the old family may not cover the new one.
- To roll back, modify the instance back to its original class.