Question

A financial services company runs a mission-critical application on an Amazon Aurora MySQL-Compatible cluster. During a faulty deployment, an application bug executed a bad UPDATE statement that silently corrupted several tables. The problem was discovered 45 minutes later. The team needs to recover the database to the exact state moments before the corruption with the least amount of downtime and without provisioning a new cluster endpoint that would require application reconfiguration. Which approach best meets these requirements?

Accepted Answer

Use Aurora Backtrack to rewind the existing cluster to a timestamp just before the bad UPDATE executed.

Answer

Restore the most recent automated snapshot to a new Aurora cluster and update the application connection string to the new endpoint.

Answer

Perform a point-in-time restore (PITR) to a new cluster at the timestamp before corruption and repoint the application.

Answer

Promote an Aurora Replica to a standalone cluster and replay binary logs up to the point before the corruption.