A media studio keeps 40 TB of NFS video on premises, needs nightly one-way sync to S3 for rendering, must preserve permissions and throttle bandwidth during business hours. Which data synchronization design meets hybrid transfer requirements?

AWS DataSync is purpose-built for this hybrid transfer because it runs scheduled, one-way NFS-to-S3 replication that preserves POSIX permissions, ownership, timestamps and metadata while providing native per-schedule bandwidth throttling to protect business-hours traffic, scaling to tens of terabytes with efficient incremental nightly syncs after initial seeding for rendering workloads. The Storage Gateway File Gateway design sounds close because it also exposes on-premises NFS backed by S3, but its concept is continuous cached file access rather than discrete scheduled replication tasks with bandwidth windows, so it cannot enforce nightly one-way sync semantics cleanly. The rsync-to-EC2 staging design satisfies nightly movement over hybrid connectivity and can retain POSIX ownership on staging volumes, yet its concept fails native S3 integration because manual copy to S3 loses NFS metadata and lacks centralized scheduling and throttling controls, adding operational fragility and extra hops. The AWS Backup design offers scheduled protection of on-premises files to vault storage, but its concept is point-in-time recovery rather than producing directly readable S3 objects with preserved permissions for render nodes, so it misses the usable S3 dataset requirement. On exams, distinguish managed replication with scheduling plus throttling from gateway caching and backup vaulting, as stems hinge on usable destination format plus timing controls. In practice, verify DataSync task reports, CloudWatch throughput, and test restored POSIX ACLs on a sample S3 prefix with the throttling window applied.