A company stores multiple Amazon Machine Images (AMIs) in an AWS account to launch Amazon EC2 instances. The AMIs contain critical data and configurations needed for operations. The company wants a solution to recover accidentally deleted AMIs quickly and with the LEAST operational overhead. Which solution meets these requirements?

Creating a retention rule in Recycle Bin is the most effective solution for recovering accidentally deleted AMIs with the least operational overhead. Recycle Bin allows you to set a retention period for deleted EBS snapshots and AMIs, automatically retaining them for a specified duration. If an AMI is accidentally deleted, it moves to the Recycle Bin and can be restored directly, preserving its original ID and attributes. Creating EBS snapshots of AMIs and storing them in a separate account adds an extra step and management overhead, as you'd need to create new AMIs from these snapshots. Copying all AMIs to another AWS account periodically is a viable disaster recovery strategy but involves higher operational overhead for ongoing synchronization and management, and it doesn't directly address accidental deletion recovery of the original AMI. Uploading AMIs to an Amazon S3 bucket is not a native or practical way to back up AMIs for direct recovery; AMIs are based on EBS snapshots, not S3 objects in this context.