This topic describes the lifecycles for MySQL community versions and ApsaraDB RDS for MySQL.
Major engine version lifecycle
After a kernel version expires, only updates to that version are affected. The expiration does not impact the creation or use of instances. For information about creating new instances, see the official announcements.
ApsaraDB RDS for MySQL extends support beyond the official lifecycle of MySQL community versions. During this extended period, ApsaraDB RDS for MySQL continues to release new versions with fixes for critical issues affecting instance security and stability. Because the MySQL community keeps some security issues confidential, ApsaraDB RDS for MySQL cannot guarantee fixes for all critical security and stability issues.
The extended support period gives you more time to upgrade the major engine version of your ApsaraDB RDS for MySQL instance. During the extended support period, upgrading the major engine version remains your best choice. For instructions on how to upgrade the major engine version, see Upgrade the major engine version.
This table lists the lifecycle dates for major MySQL community versions and their ApsaraDB RDS for MySQL counterparts.
Some dates in the table are estimates and may be revised before the end-of-life (EOL) or end-of-support date. The actual announced dates take precedence.
Major engine version | Community release | RDS release | Community EOL | RDS support end |
MySQL 8.4 | July 18, 2023 | March 2026 | April 2032 (estimated) | / |
MySQL 8.0 | April 19, 2018 | May 2019 | April 21, 2026 | / |
MySQL 5.7 | October 21, 2015 | November 2016 | October 21, 2023 | October 21, 2028 (estimated) |
MySQL 5.6 | February 5, 2013 | December 2014 | February 5, 2021 | February 5, 2028 (estimated) |
MySQL 5.5 | December 8, 2010 | February 2012 | December 8, 2018 | December 8, 2021 |