End-of-life for t2 RDS instances

Hi

If you want to test out if there are any impacts from changing the RDS instance type, I would suggest taking a snapshot of the database and then restoring the snapshot with the new instance type. Let's say you have a t2.medium then we take a snapshot of the existing database and then restore it with a t3.medium so you can determine if there are any issues and then apply the upgrade to the production instance.

RDS Snapshot -> https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_CreateSnapshot.html

PS - Unless you are downgrading the instance changing the instance type would not cause any issues, however, there will be downtime during the upgrade.

I beleive you can still purchase t2 if you wanted to for testing. Ensure when selecting Instinet Class, switch on Include Previous Generation Classes and t2 appears.

You should be able to restore a t2 snapshot and test your upgrade procedure.

I'd like to select both answers as accepted because both contain useful information, but I don't think is possible. Again many thanks to both. Here I'll list what I have tested, in case somebody else may need to do the same process.

Our instance is a t2.micro with 20GB of disk space - your mileage may vary.

1. created a snapshot of the current instance - took about 5 mins
2. restored the snapshot in another t2.micro instance
3. updated the instance type from t2.micro to t3.micro and also updated the mysql version (more about this later) - took about 16 mins - I chose to apply the changes immediately
4. checked access to data, tested some queries and so on

I'm a little surprise that my original instance has minor version upgrades turned on, but it is 2 minor versions behind (on 8.0.28, when 8.0.32 and 8.0.33 are available). This is the reason why I also updated the mysql version at the same time as the instance type.