Which solution will meet these requirements with the LEAST administrative overhead?
Create an AWS Storage Gateway Volume Gateway. Create a file share that uses the required client protocol. Connect the application server to the file share.
Create an AWS Storage Gateway Tape Gateway. Configure tapes to use Amazon S3. Connect the application server to the Tape Gateway.
Create an Amazon EC2 Windows instance. Install and configure a Windows file share role on the instance. Connect the application server to the file share.
Create an Amazon FSx for Windows File Server file system. Connect the application server to the file system.
Explanations:
AWS Storage Gateway Volume Gateway is primarily designed for block storage, and while it supports file shares, it is not the most straightforward solution for SMB access with minimal overhead compared to FSx.
The Tape Gateway is meant for backup solutions and does not provide file share access or SMB support. It is not suitable for a shared storage solution for a media application.
Creating an EC2 instance with a Windows file share requires significant administrative overhead, including instance management, scaling, and maintenance, making it less ideal for the requirements.
Amazon FSx for Windows File Server is a fully managed service that provides native SMB support with minimal administrative overhead. It is designed for file sharing and is the best fit for the company’s needs.
I plot that the answer is:
Create an Amazon FSx for Windows File Server file system. Connect the application server to the file system.