Which solution will meet these requirements in the MOST operationally efficient way?
Write an AWS Lambda function that schedules nightly snapshots of the application’s EBS volumes and copies the snapshots to a different Region.
Create a backup plan by using AWS Backup to perform nightly backups. Copy the backups to another Region. Add the application’s EC2 instances as resources.
Create a backup plan by using AWS Backup to perform nightly backups. Copy the backups to another Region. Add the application’s EBS volumes as resources.
Write an AWS Lambda function that schedules nightly snapshots of the application’s EBS volumes and copies the snapshots to a different Availability Zone.
Explanations:
While using AWS Lambda to schedule nightly snapshots of EBS volumes is a valid approach, it does not provide a comprehensive solution for backing up EC2 instance configurations and is less efficient compared to AWS Backup, which can manage multiple resources together. Additionally, it requires custom code for snapshot management and copying, increasing operational overhead.
AWS Backup allows for creating a backup plan that can automate nightly backups of both the EC2 instances and EBS volumes. It provides a built-in capability to copy backups to another Region, ensuring data recovery in a different location. This option is the most operationally efficient as it centralizes backup management without requiring custom scripting.
While AWS Backup can perform nightly backups of EBS volumes, it does not encompass the entire configuration of the application if EC2 instances are not included as resources. This limits the backup’s effectiveness, as only data volumes are backed up, leaving instance configurations unprotected. Additionally, it lacks operational efficiency compared to including all relevant resources in the backup plan.
This option focuses on taking snapshots of EBS volumes and copying them to another Availability Zone instead of a different Region. While it may offer some level of redundancy within the same Region, it does not meet the requirement for cross-region recoverability. Like option A, it also involves custom coding, which adds to operational complexity compared to using AWS Backup.