Which solution will meet these requirements?
Create a second CloudFormation template that can recreate the EC2 instances in the secondary Region. Run daily multivolume snapshots by using AWS Systems Manager Automation runbooks. Copy the snapshots to the secondary Region. In the event of a failure launch the CloudFormation templates, restore the EBS volumes from snapshots, and transfer usage to the secondary Region.
Use Amazon Data Lifecycle Manager (Amazon DLM) to create daily multivolume snapshots of the EBS volumes. In the event of a failure, launch the CloudFormation template and use Amazon DLM to restore the EBS volumes and transfer usage to the secondary Region.
Use AWS Backup to create a scheduled daily backup plan for the EC2 instances. Configure the backup task to copy the backups to a vault in the secondary Region. In the event of a failure, launch the CloudFormation template, restore the instance volumes and configurations from the backup vault, and transfer usage to the secondary Region.
Deploy EC2 instances of the same size and configuration to the secondary Region. Configure AWS DataSync daily to copy data from the primary Region to the secondary Region. In the event of a failure, launch the CloudFormation template and transfer usage to the secondary Region.
Explanations:
While this option describes creating a second CloudFormation template and using AWS Systems Manager Automation for snapshots, it does not optimize operational efficiency as much as other solutions. Managing the snapshot lifecycle manually through Automation runbooks adds complexity and could lead to operational overhead.
This option mentions using Amazon Data Lifecycle Manager (DLM) for daily multivolume snapshots, which is effective for backup but lacks the capability to directly copy snapshots to another region. DLM can create and manage snapshots but does not facilitate cross-region copy automatically, which is necessary for compliance with the requirement to maintain backups in a separate region.
AWS Backup provides a comprehensive solution for scheduled backups of EC2 instances, including the ability to copy backups to a secondary region. This meets the requirement of restoring EC2 instances and their configurations within 1 business day, with data loss not exceeding one day’s worth. It optimizes operational efficiency by automating backup management without manual intervention.
This option involves deploying EC2 instances in the secondary region and using AWS DataSync to copy data. However, this approach does not specifically address the requirements for backing up EBS volumes or maintaining instance configurations. DataSync is primarily for transferring files, not for managing snapshots or EC2 configurations, which are critical for a complete recovery solution.
As far as I’m aware, the answer is:
Use AWS Backup to create a scheduled daily backup plan for the EC2 instances. Configure the backup task to copy the backups to a vault in the secondary Region. In the event of a failure, launch the CloudFormation template, restore the instance volumes and configurations from the backup vault, and transfer usage to the secondary Region.