What should a solutions architect do to meet these requirements?
Deploy and configure Amazon FSx for Windows File Server on AWS. Move the on-premises file data to FSx for Windows File Server. Reconfigure the workloads to use FSx for Windows File Server on AWS.
Deploy and configure an Amazon S3 File Gateway on premises. Move the on-premises file data to the S3 File Gateway. Reconfigure the on-premises workloads and the cloud workloads to use the S3 File Gateway.
Deploy and configure an Amazon S3 File Gateway on premises. Move the on-premises file data to Amazon S3. Reconfigure the workloads to use either Amazon S3 directly or the S3 File Gateway. depending on each workload’s location.
Deploy and configure Amazon FSx for Windows File Server on AWS. Deploy and configure an Amazon FSx File Gateway on premises. Move the on-premises file data to the FSx File Gateway. Configure the cloud workloads to use FSx for Windows File Server on AWS. Configure the on-premises workloads to use the FSx File Gateway.
Explanations:
Moving all data directly to FSx for Windows File Server on AWS would introduce high latency for on-premises workloads accessing data over VPN and would require significant reconfiguration of workloads to adapt to AWS-only storage.
Amazon S3 File Gateway provides access to data stored in S3 rather than in a file server format, requiring significant changes to file access patterns. It does not meet the need for native file system support compatible with existing file shares.
S3 File Gateway and Amazon S3 do not offer the same SMB/NFS file access protocols as FSx for Windows File Server, and reconfiguring workloads to use S3 directly would introduce operational overhead and require changing existing access patterns.
Using FSx for Windows File Server with an FSx File Gateway on-premises provides low-latency access for both on-premises and AWS workloads while maintaining compatibility with Windows file systems and minimizing operational overhead.