Which solution meets these requirements with the LEAST operational overhead?
Create an AWS Lambda function that uses the Docker container image with an Amazon S3 mounted volume that has more than 50 GB of space.
Create an AWS Lambda function that uses the Docker container image with an Amazon Elastic Block Store (Amazon EBS) volume that has more than 50 GB of space.
Create an Amazon Elastic Container Service (Amazon ECS) cluster that uses the AWS Fargate launch type. Create a task definition for the container image with an Amazon Elastic File System (Amazon EFS) volume. Create a service with that task definition.
Create an Amazon Elastic Container Service (Amazon ECS) cluster that uses the Amazon EC2 launch type with an Amazon Elastic Block Store (Amazon EBS) volume that has more than 50 GB of space. Create a task definition for the container image. Create a service with that task definition.
Explanations:
AWS Lambda functions have a limitation on the file system size for temporary storage (512 MB). They do not support Amazon S3 mounted volumes directly in the way required for temporary file storage.
AWS Lambda does not support attaching Amazon Elastic Block Store (EBS) volumes. EBS volumes require an EC2 instance to be mounted and cannot be used in a Lambda function.
Using Amazon ECS with Fargate allows for serverless container management. Fargate can utilize Amazon EFS as a persistent file system, which can easily accommodate the required 50 GB of storage for temporary files with minimal operational overhead.
While ECS with the EC2 launch type can provide EBS volumes, this option is not serverless. It requires managing EC2 instances, which increases operational overhead, contrary to the requirement for a serverless architecture.