How to Fix AWS Aurora MySQL Failing Over Stuck for Months

Select Language:

If your Aurora MySQL cluster has been stuck in a “Failing over” state for a long time, it can be quite frustrating. Usually, this kind of issue is unusual, and fixing it might require help from AWS Support.

Standard troubleshooting, like rebooting your cluster, might not work if the cluster is stuck in an abnormal state. In this situation, the best step is to contact AWS Support directly. They have special access to the backend systems and can look into what’s causing the problem using your cluster ID and instance ID.

Here’s what you should do:

1. Log into your AWS Console and go to the AWS Support Center to open a support case.
2. When submitting your case, include your cluster ID and instance IDs so support can easily find your resources.
3. Clearly explain the problem: mention how long the cluster has been in this failing state and what troubleshooting steps you’ve already tried.

While waiting for AWS Support, check if there’s any scheduled maintenance on your cluster that might be related to this issue. You can find this information in the RDS console by selecting your database instance and viewing the Maintenance & backups tab.

Because this problem is preventing important tasks like upgrades or configuration changes, it’s a good idea to request urgent assistance by setting an appropriate severity level, depending on your support plan. AWS Support can then investigate the problem more deeply and help get your cluster back to normal.

Getting help quickly can make a big difference in restoring your database to working order.