Which solution will meet these requirements?
Migrate the application to run as containers on Amazon Elastic Container Service (Amazon ECS). Use Amazon S3 for storage.
Migrate the application to run as containers on Amazon Elastic Kubernetes Service (Amazon EKS). Use Amazon Elastic Block Store (Amazon EBS) for storage.
Migrate the application to Amazon EC2 instances in a Multi-AZ Auto Scaling group. Use Amazon Elastic File System (Amazon EFS) for storage.
Migrate the application to Amazon EC2 instances in a Multi-AZ Auto Scaling group. Use Amazon Elastic Block Store (Amazon EBS) for storage.
Explanations:
Amazon S3 is object storage, not a file system. It doesn’t support a standard file system structure required by the application.
Amazon EBS is block storage and doesn’t provide a standard file system structure across multiple instances, which is necessary for high availability and scaling.
Amazon EFS is a managed file storage service that supports a standard file system interface, scales automatically, and is highly available across multiple Availability Zones, making it suitable for large file sizes.
While Amazon EBS provides block storage, it is not designed for a shared file system and does not support high availability across multiple instances without additional setup, making it unsuitable for the requirements.
From my point of view, the answer is:
Migrate the application to Amazon EC2 instances in a Multi-AZ Auto Scaling group. Use Amazon Elastic File System (Amazon EFS) for storage.
I arrange that the answer is:
Migrate the application to Amazon EC2 instances in a Multi-AZ Auto Scaling group. Use Amazon Elastic File System (Amazon EFS) for storage.