A research company runs a simulation application on Linux that writes intermediate data to an NFS share every 5 minutes. A Windows visualization desktop application reads that output and requires SMB. The company currently maintains two synchronized file systems, causing duplication. They must migrate to AWS without changing either application. Which solution meets these requirements?

The correct solution is to migrate the simulation application to Linux Amazon EC2 instances and the visualization application to Windows EC2 instances, configuring Amazon FSx for NetApp ONTAP for storage. FSx for NetApp ONTAP supports both NFS and SMB protocols concurrently, allowing the Linux simulation application to write to an NFS share and the Windows visualization application to read from an SMB share on the same file system without application changes. Incorrect options: Migrating to AWS Lambda or Amazon ECS would require significant application refactoring, as the question states no application changes are allowed. S3 or FSx File Gateway would not natively provide both NFS and SMB access to the same dataset in the required manner. Using Amazon SQS is for message queuing, not for sharing file system data between applications.