A company runs self-managed Microsoft SQL Server on Amazon EC2 with Amazon EBS. Daily snapshots of the EBS volumes are taken. Recently, all EBS snapshots were accidentally deleted by a snapshot cleaning script that removed expired snapshots. A solutions architect must update the architecture to prevent data loss without keeping snapshots indefinitely. Which solution meets these requirements with the LEAST development effort?

The correct answer is to create a 7-day EBS snapshot retention rule in Recycle Bin and apply the rule to all snapshots. Amazon EBS Recycle Bin allows you to set retention rules for deleted snapshots, preventing accidental permanent deletion for a specified period. This directly addresses the problem of accidental deletion by providing a recovery window, and it requires minimal development effort as it's a native AWS feature. Changing the IAM policy to deny EBS snapshot deletion would prevent the cleaning script from working at all, which is not the goal; the company wants to delete expired snapshots, just not accidentally. Copying snapshots to another AWS Region or to Amazon S3 Standard-IA are valid disaster recovery strategies, but they are more complex and involve higher operational overhead than simply using the Recycle Bin for accidental deletion recovery within the same region.