Question

A media company runs an on-premises NFS file share (approximately 40 TB) that feeds a legacy video-rendering pipeline. The company is migrating the rendering workload to EC2 and EFS in AWS over a 6-week transition window. During the transition, files continue to be created and modified on-premises, and the team needs those changes reflected in EFS on a recurring nightly basis until final cutover. The on-premises site has a 1 Gbps Direct Connect link with spare capacity at night. Which approach minimizes operational effort while keeping the AWS copy incrementally up to date?

Accepted Answer

Deploy an AWS DataSync agent on-premises, create a task from the NFS location to the EFS location, and schedule it to run nightly so only changed data is transferred each run.

Answer

Order an AWS Snowball Edge device, copy the 40 TB once, ship it to AWS, and load it into EFS; repeat the Snowball order weekly to capture incremental changes.

Answer

Write a cron job on the NFS server that uses the AWS CLI to sync files to an S3 bucket, then run a Lambda function to copy objects from S3 into EFS each night.

Answer

Use AWS Database Migration Service (DMS) with change data capture to continuously replicate the file share into EFS until the final cutover.