Which AWS Solution Lets You Use NFS to Store and Retrieve Objects in Amazon S3?

Why the Answer Is Correct

AWS Storage Gateway file gateway is a hybrid storage service that presents an Amazon S3 bucket through standard file protocols, including NFS (v3 and v4.1) and SMB, so on-premises or EC2 applications can read and write S3 objects as ordinary files. Objects written through the file share are stored as objects in S3, and local caching accelerates frequently accessed data while the bucket remains the source of truth. That direct mapping between a file-protocol front end and S3 object storage is exactly what the question describes: using protocols such as NFS to store and retrieve objects in Amazon S3. Marley captured the intent succinctly, noting that the file gateway "allows you to use NFS to access objects in S3."

Why the Other Options Are Wrong

Amazon FSx for Lustre (A) is a managed, high-performance parallel file system for HPC, ML, and compute-intensive workloads; although it supports NFS and can link to an S3 bucket to read or write data, that link behaves as a caching/lazy-loading layer for the file system rather than a general-purpose file interface onto S3. As veljkosbbb put it, FSx for Lustre is "primarily intended for use cases requiring high-performance computing (HPC) and parallel data processing," which is not the scenario in the question. Kilobay1 argued for A on the basis that FSx for Lustre "supports the Network File System (NFS) protocol and can be linked to Amazon S3," which is true but describes an optimization feature, not the service's core purpose. AWS Storage Gateway volume gateway (B) presents block storage (iSCSI) backed by S3 snapshots, so it does not offer NFS at all. Amazon EFS (D) is a scalable NFS file system for Linux workloads across AWS compute services, but it does not store and retrieve objects in an S3 bucket.

Community Comment Notes

Community sentiment aligns strongly with the file gateway, and two commenters restated it plainly — ShaiTay simply posted "AWS Storage Gateway file gateway," and Meow7 confirmed "c is correct" before asking for help with unrelated discussion questions. veljkosbbb gave the most useful reasoning, drawing the line between FSx for Lustre's compute-oriented design and the gateway's role of exposing S3 over NFS. Kilobay1's counter-argument for FSx for Lustre is worth reading because it shows the exact trap: NFS support plus S3 linkage exists on both services, so the deciding factor is the service's intended purpose, not a feature checklist. Taken together, the comments reinforce that purpose (presenting S3 as files) beats incidental capability (caching S3 into a fast file system).