Which solution will meet these requirements with the LEAST operational overhead?
Create Amazon Elastic Block Store (Amazon EBS) snapshots of the AMIs. Store the snapshots in a separate AWS account.
Copy all AMIs to another AWS account periodically.
Create a retention rule in Recycle Bin.
Upload the AMIs to an Amazon S3 bucket that has Cross-Region Replication.
Explanations:
While creating EBS snapshots of AMIs and storing them in a separate account provides a backup, it requires more operational overhead to manage snapshots and restore AMIs from them compared to other options.
Copying all AMIs to another AWS account periodically adds operational overhead and complexity. This method involves manual processes or scheduling, which can be cumbersome compared to automatic solutions.
Creating a retention rule in the Recycle Bin allows for the quick recovery of accidentally deleted AMIs. This option requires minimal operational overhead as it automatically manages the retention and recovery of deleted items.
Uploading AMIs to an S3 bucket with Cross-Region Replication is not a standard practice for AMI recovery and requires more operational management. This option also introduces latency in AMI restoration compared to direct AMI recovery methods.