Which solution will meet these requirements?
Migrate both applications to AWS Lambda. Create an Amazon S3 bucket to exchange data between the applications.
Migrate both applications to Amazon Elastic Container Service (Amazon ECS). Configure Amazon FSx File Gateway for storage.
Migrate the simulation application to Linux Amazon EC2 instances. Migrate the visualization application to Windows EC2 instances. Configure Amazon Simple Queue Service (Amazon SQS) to exchange data between the applications.
Migrate the simulation application to Linux Amazon EC2 instances. Migrate the visualization application to Windows EC2 instances. Configure Amazon FSx for NetApp ONTAP for storage.
Explanations:
AWS Lambda is not suitable for running applications that require persistent state or continuous execution, such as the simulation and visualization applications. Additionally, AWS Lambda does not support NFS and SMB natively, making it difficult to exchange data between the applications without code changes.
While Amazon ECS is a suitable option for containerized applications, it does not address the requirement for a shared SMB file system that the visualization application needs. Amazon FSx File Gateway supports SMB, but it is not designed to work directly with ECS for these specific applications without code modifications.
Migrating to EC2 instances allows both applications to run in their native environments; however, using Amazon SQS for data exchange does not satisfy the requirement for shared file access. The visualization application relies on direct file system access (SMB), which SQS does not provide.
This option allows the simulation application to run on Linux EC2 instances and the visualization application on Windows EC2 instances while using Amazon FSx for NetApp ONTAP, which supports both NFS and SMB protocols. This setup meets the requirements for seamless data access without code changes, enabling efficient data sharing between the applications.