A company runs its media rendering application on premises. The company wants to reduce storage costs and has moved all data to Amazon S3. The on-premises rendering application needs low-latency acces

Mountpoint for Amazon S3 allows direct S3 access from on-premises but does not provide local caching for low-latency access to frequently used data and is subject to network latency over the internet.

An Amazon S3 File Gateway provides an on-premises file interface (NFS or SMB) with local caching, allowing the media rendering application to access data in Amazon S3 with low latency for frequently accessed files while leveraging the cost-effectiveness and scalability of S3 for backend storage.

Copying data from S3 to Amazon FSx for Windows File Server (a cloud service) and accessing it over AWS Direct Connect would increase complexity and costs, negating the cost reduction benefit of S3 as primary storage.

Configuring an on-premises file server adds local storage costs and management overhead, and accessing S3 directly via its API from on-premises would not guarantee low-latency access for all operations without a local caching mechanism.