X
Lab complete!
Now that you have completed this lab, make sure to update your Well-Architected review if you have implemented these changes in your workload.
Click here to access the Well-Architected Tool
Lab 1 - Change Database Instance Type
- Migration Methodologies
- Preparation
- Lab 1 - Change Database Instance Type
- Lab 2 - Promote Read Replica
- Lab 3 - Failover to Read Replica
- Lab 4 - Restore from snapshot
- Cleanup
Overview
In this lab you will take the RDS MySQL database that was created in the Preparation step, and migrate it from the x86-64 instance it was built on, to a Graviton based instance.
This migration method works for all RDS databases that support AWS Graviton, including Amazon Aurora.
With this migration type, applications can continue to use the existing endpoints.
Check the database is fully created
- From the RDS dashboard, go to databases in the side menu.
- Check the
mysql-lab1database is in an Available state (click refresh to update the current state).
Change the instance type from x86-64 to Graviton
Once the database is in the available state, select the database radio button and click Modify.
On the Modify DB Instance page, change the instance type to db.t4g.micro.
Leave all other settings as they are and scroll all the way down and click Continue
In Schedule modifications, select Apply Immediately
Click Modify DB Instance
The database will be modified and then restart on the graviton instance type, clicking refresh on the console will show the status of the change.
When the database is in Available status and running on Graviton you have successfully completed this lab.
