Which solution will meet the backup requirements with the LEAST operational overhead?
Use the Amazon S3 CopyObject API operation with multipart upload to copy the existing data to Amazon S3. Use the CopyObject API operation to replicate new data to Amazon S3 daily.
Create a backup plan in AWS Backup to back up the data to Amazon S3. Schedule the backup plan to run daily.
Install the AWS DataSync agent as a VM that runs on the on-premises hypervisor. Configure a DataSync task to replicate the data to Amazon S3 daily.
Use an AWS Snowball Edge device for the initial backup. Use AWS DataSync for incremental backups to Amazon S3 daily.
Explanations:
Using the Amazon S3 CopyObject API requires manual coding for data uploads and incremental backups, resulting in high operational overhead. This approach lacks built-in automation and custom filtering capabilities for daily backups.
AWS Backup is primarily designed for backing up AWS resources and does not support direct backups from on-premises files to Amazon S3, limiting its applicability in this scenario. It lacks the capability to filter specific directories efficiently.
AWS DataSync automates the transfer of data from on-premises to Amazon S3, allowing for custom filtering during the synchronization process. It is specifically designed for this purpose and can handle daily incremental backups with minimal operational overhead.
While AWS Snowball Edge can be used for large initial data transfers, it introduces additional complexity and logistics for subsequent daily incremental backups, which would still require a different solution like DataSync, leading to higher operational overhead overall.
I outline that the answer is:
Install the AWS DataSync agent as a VM that runs on the on-premises hypervisor. Configure a DataSync task to replicate the data to Amazon S3 daily.