Which solution will meet these requirements?
Create an Aurora Replica. Promote the replica to replace the primary DB instance.
Create an AWS Lambda function to restore an automatic backup to the existing DB cluster.
Use backtracking to rewind the existing DB cluster to the desired recovery point.
Use point-in-time recovery to restore the existing DB cluster to the desired recovery point.
Explanations:
Creating an Aurora Replica and promoting it does not allow rolling back to a specific point-in-time. It would replace the primary DB instance but won’t fulfill the requirement to roll back to a previous recovery point.
An AWS Lambda function cannot directly restore an automatic backup to an existing DB cluster. Lambda is not intended for managing DB restores in this way.
Backtracking allows rewinding the existing DB cluster to a specific point within the past 72 hours, meeting the requirement for rolling back to a recovery point within this timeframe.
Point-in-time recovery (PITR) restores the DB cluster to a specific point in time but requires creating a new DB cluster. It cannot be done within the same production DB cluster as stated in the requirements.
I infer that the answer is:
Use backtracking to rewind the existing DB cluster to the desired recovery point.
I systematize that the answer is:
Use backtracking to rewind the existing DB cluster to the desired recovery point.