AWS Graviton instances are EC2 instances powered by AWS-designed ARM-based processors. They offer better price-performance compared to traditional x86-based instances (Intel & AMD), with potential savings of 15–19%.
Using Graviton with RDS is simple, more efficient, and a better price/performance.
Subtitles are available in English, French and Spanish. Click here to get the full masterclass.
How to identify?
You can identify opportunities to migrate to Graviton using the following methods:
From our Cost Optimizations Report, check at EC2 or RDS Upgrade or RightSize sections.
In AWS Console, navigate to the Cost Optimization Hub and filter for the recommended action Migrate to Graviton:
In AWS Compute Optimizer, compare multiple instance options for Graviton compatibility and performance:
How to fix?
EC2:
Do not switch if your software doesn’t support ARM (e.g., legacy x86 applications) or if your application is Windows-based.
Check compatibility: Ensure your application supports ARM on test servers (e.g., t4g).
Use Multi-Arch Docker images if running containers.
RDS:
RDS is a managed service, so AWS handles all compatibility issues related to the ARM architecture. You don’t need to worry about low-level driver issues.
Note: changing RDS instance types will incur a downtime. Plan this change during your maintenance window budget 30 minutes for the instance switch.
RDS (Console)
Login to to the Console.
Choose Databases, then choose the DB instance that you want to modify.
Choose Modify. The Modify DB instance page appears.
Change the instance size to a graviton (ie. db.m6g.large) instance, following whatever Compute Optimizer or Trusted Advisor advises.
Choose Continue.
Choose Apply immediately to apply the changes immediately (For more information, see Using the Apply Immediately setting.
On the confirmation page, choose Modify DB instance.
The instance should go to a Modifying state. Wait for the instance to become available, then validate and start your applications. There should be no other impact.
RDS (Terraform)
In your terraform configuration, find your RDS resource aws_db_instance.
Modify the instance_class parameter to your desired Graviton instance class (e.g., db.m6g.large):
Run your terraform plan and confirm.
Run the terraform apply through your CICD system. Ensure dev/lower environments first.
Graviton - History
In 2018, AWS released the first Graviton (A1 instance family).
In 2020, the second generation, Graviton2, is released, with AWS promising 40% improved price/performance over 5th generation Intel and AMD instances and an average of 72% reduction in power consumption (M6g, C6g, R6g, T4g, X2gd, G5g, Im4gn, Is4gen, I4g).
In 2022, AWS made available Graviton3 processors as part of its 7th generation EC2 instances, offering a further 25% better compute performance over Graviton2.
EC2 instances: C7g, M7g, R7g.
RDS instances: db.r7g, db.m7g.
In 2024, AWS released Graviton4 and claims it is 40% faster for databases, 30% faster for web applications, and 45% faster for large Java applications than Graviton3.
EC2 instances: R8g, X8g, C8g, M8g, I8g.
RDS instances: db.r8g, db.m8g.