Amazon RDS MySQL 8.0 standard support ends on July 31. Starting August 1, instances that remain on MySQL 8.0 will automatically enter paid extended support unless you explicitly disable it. In us-east-1, the initial charge is $0.10 per vCPU-hour and increases in later years, which could add roughly $292 per month for a Multi-AZ db.r5.large.
The databases most likely to be missed are idle development and staging instances. They may continue running normally, but their costs will increase. There is an engine-lifecycle-support setting that can prevent automatic enrollment, although those instances will no longer receive patches after the cutoff, so that option is better suited to disposable environments.
Has anyone completed the MySQL 8.0 to 8.4 upgrade? Was an in-place upgrade or a blue/green deployment smoother, and did you encounter any application compatibility issues?
2 Answers
Blue/green worked very well for us too. The cutover was effectively zero-downtime, and we didn’t run into any significant problems during the upgrade.
We had around 20 databases owned by different teams, so we used blue/green deployments throughout. For each development environment, we created a small temporary instance and tested whether the application worked correctly on the newer MySQL version. That made the final cutover straightforward with almost no downtime and no major surprises.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures