It seems likely that you have a data inconsistency in the innodb tables space. This gets propagated into a new read replica or a restore from backups. I'd recommend you use mysqldump to extract data from your instance and reload it back into a new instance to fix the metadata inconsistency.
There was a corrupted index on a table. reading or writing a specific row in the table would cause the server to reboot. I created a new database from scratch from the code, and then transferred all records semi-manually using MANY mysqldump statements over several weeks - the db is 11TB.
No problems since.
RDS Free Storage Space is going downasked 7 months ago
Free Tier - EC2 MySQL or RDS MySQLAccepted Answerasked 3 years ago
RDS Instance not triggering an storage auto-scaling event.asked 3 months ago
RDS instance keeps rebootingasked 4 years ago
RDS Instance stuck in rebooting (no connections)asked 6 months ago
$0.115 per GB-month of provisioned gp2 storage running MySQL | I have created only 3 tables in my database and it doesn't contain any data at all. My bill shows 169GB of usage just for 12 Days. HELP!asked 6 months ago
MySQL RDS instance stuck rebooting status over 4 hoursasked 2 years ago
Can I import an RDS uncrypted mysql snapshot to an RDS encrypted mysql?Accepted Answerasked 6 months ago
RDS MariaDB free tierasked 2 months ago
Cannot modify RDS instanceasked 3 months ago