RDS global clusters should run on a supported Aurora MySQL version
Flags Aurora MySQL global clusters on an engine version below the minimum AWS publishes for this control, unless it is a long-term support release; such versions stop getting critical patches and can incur RDS Extended Support charges. The finding's Region is where the scan reads global clusters, not where their member clusters run.
- service
- RDS
- severity
- High
- scope
- evaluated in every region
How to fix it
In the console
RDS → Databases → the global database → Modify
With the AWS CLI
aws rds modify-global-cluster --global-cluster-identifier <global-cluster-id> --engine-version <engine-version> --allow-major-version-upgrade --region <region>
See which of your accounts this check is failing on.
Book a demo