- Newest
- Most votes
- Most comments
RDS, as PaaS, doesn't support all possible versions and each version has end-of-support date. When that date is reached, AWS will automatically upgrade minor versions. In your case 8.0.20 did reach it's end-of-support and got upgraded to 8.0.28 that will remain supported until June 2023.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html
Q: What happens when an RDS DB engine version is deprecated?
When a minor version of a database engine is deprecated in Amazon RDS, we will provide a three (3) month period after the announcement before beginning automatic upgrades. At the end of the this period, all instances still running the deprecated minor version will be scheduled for automatic upgrade to the latest supported minor version during their scheduled maintenance windows.
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- asked 5 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
Thank you very much. We didn't know that. However, that upgrade caused the RDS to not respond to connections for 7.5 hours and we noticed that when we woke up. We had to reboot the RDS. Shouldn't the connectivity come back automatically? Thankfully that happened during the night, but, still, that is a problem. Thisi s the reason we believe that it is a bug with the RDS autoupgrade mechanism. Thank you for your quick reply
To maximize the db availability you could consider multi-az and/or blue-green deployments. To find what might have happened for your db upgrade you can open a ticket for AWS support if you have support enabled the account.
https://aws.amazon.com/rds/features/multi-az/ https://aws.amazon.com/blogs/aws/new-fully-managed-blue-green-deployments-in-amazon-aurora-and-amazon-rds/
Awesome. Thanks for the reply!