-
Bug
-
Resolution: Fixed
-
Critical
-
5.0, 4.5.6, 4.4.10, 4.1.20
-
6
-
Team Hedgehogs 2025 Sprint 2.1, Team Hedgehogs 2025 Sprint 2.2
Background
AWS Aurora is Amazon's highly scalable and highly available SQL DB service. It used by mainly organisations to host their Moodle LMS instances. Essentially it is a fork of the community versions of MySQL and Postgres (both engines are available). AWS then essentially adds their own patches (security etc).
For the most part Aurora is feature compatible with the community version of the database engine (either MySQL or Postgres).
In LMS 3.10 (MDL-58931) explicit support was added for Aurora MySQL. This is essentially a thin wrapper around the existing MySQL drivers. This allowed auroramysql to by set as the dbtype in config.php and fixed some compatibility issues that were present at the time. The code has not changed much since then.
Historically, AWS have been slow to update the major version of MySQL used by Aurora, instead they have tended to backport patches. They do upgrade the major version eventually.
Problem
In LMS 5.0 the minimum version of MySQL required was upped from 8.0 to 8.4 (see MDL-83470), this was due to the impending EOL for MySQL 8.0 (as part of the LMS lifecycle) and that 8.4 has been released for more than 12 months.
However, AWS Aurora only supports at a maximum MySQL 8.0.39.
See: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html
This means that anyone using AWS Aurora MySQL cannot install or upgrade currently to LMS 5.0, without hacking the environment.xml file or changing to Postgres.
Proposed Solution
Update the support introduced MDL-58931 to allow AWS Aurora with a minimum version of 3 for LMS 5.0
This will also require including this in the LMS requirements policy going forward.
Update documentation etc. that for organisations using AWS Aurora MySQL to explicitly set the dbtype in config.php to auroramysql
More info: