Mysql RDS reboot with failover

Hello there is already an article in repost, Please checking information here https://repost.aws/knowledge-center/rds-mysql-stuck-rebooting

Additional Information from Side,

Try Force Failover:

aws rds reboot-db-instance --db-instance-identifier campayn-production-ca --force-failover

Data Loss: Forced failover might lead to some data loss from the most recent transactions. Recovery Planning: After failover, carefully examine the state of the new primary (formerly the secondary) to determine if any data recovery steps are needed from the corrupted instance.

Another Alternatives:

• Create New instance point in restore with name campayn-production-ca-new
• Rename existing campayn-production to campayn-production-old
• change the new db create with name campayn-production so this instance will be come NEW production.

Hello ,

Alternative is to restore the Automated backup or use the last good snapshot ,

please see

Amazon RDS Backup and Restore https://aws.amazon.com/rds/features/backup/

Restoring from a DB snapshot https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RestoreFromSnapshot.html

Hello,

When I tried to use cli force command I got:

An error occurred (InvalidDBInstanceState) when calling the RebootDBInstance operation: Can only reboot db instances with state in: available, storage-optimization, incompatible-credentials, incompatible-parameters. Instance campayn-production-ca has state: rebooting.

Thank you