What should a solutions architect do to meet these requirements?
Create an Amazon S3 Standard bucket with access to the web servers.
Configure an Amazon CloudFront distribution with an Amazon S3 bucket as the origin.
Create an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system on all web servers.
Configure a General Purpose SSD (gp3) Amazon Elastic Block Store (Amazon EBS) volume. Mount the EBS volume to all web servers.
Explanations:
Amazon S3 is an object storage service, and while it can be used to store files, it cannot be mounted as a file system directly on Linux-based servers without using additional services (like S3FS or an application layer) which would require changes to the application.
Amazon CloudFront is a content delivery network (CDN) that serves cached content from an origin, such as an S3 bucket. However, this does not provide a shared file system for the web servers, and changes to the application may be needed to accommodate the CDN.
Amazon Elastic File System (EFS) is a managed file storage service that can be mounted by multiple EC2 instances at the same time. It provides a shared file system, allowing the web servers to access files concurrently without requiring any application changes.
Amazon Elastic Block Store (EBS) volumes are designed for use with a single EC2 instance at a time. While they can be mounted to an instance, they cannot be shared among multiple web servers without requiring a more complex setup, which may involve additional changes to the application.
From what I’ve seen, the answer is:
Create an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system on all web servers.