Which solution will meet these requirements?
Create an AWS DataSync agent in the corporate data center. Create a data transfer task Start the transfer to an Amazon S3 bucket.
Back up the data to AWS Snowball Edge Storage Optimized devices. Ship the devices to an AWS data center. Mount a target Amazon S3 bucket on the on-premises file system.
Use rsync to copy the data directly from local storage to a designated Amazon S3 bucket over the Direct Connect connection.
Back up the data on tapes. Ship the tapes to an AWS data center. Mount a target Amazon S3 bucket on the on-premises file system.
Explanations:
AWS DataSync is designed for efficient data transfer between on-premises storage and AWS services like S3. It supports ongoing changes, allowing data access and updates during the transfer, meeting the company’s requirement for continuous access.
AWS Snowball Edge is a viable option for large data transfers, but it involves physical shipping of devices, which would not allow access to data during the transfer. This option is disruptive and does not meet the requirement for continuous data access.
While rsync could transfer the data over the Direct Connect connection, it is not an optimized solution for large data migrations like AWS DataSync. Additionally, rsync does not handle incremental transfers efficiently in this context and may not support continuous access during the transfer.
Shipping tapes to an AWS data center is a slow process and would cause significant disruption as the company would not be able to access or update the data during the transfer. This method does not align with the need for a seamless data migration.