A company has a business system that generates hundreds of reports each day. The business system saves the reports to a network share in CSV format. The company needs to store this data in the AWS…

Question

Options

• AUse AWS DataSync to transfer the files to Amazon S3. Create a scheduled task that runs at the
• BCreate an Amazon S3 File Gateway. Update the business system to use a new network share
• CUse AWS DataSync to transfer the files to Amazon S3. Create an application that uses the
• DDeploy an AWS Transfer for SFTP endpoint. Create a script that checks for new files on the

• A
  6% (2)
• B
  74% (23)
• C
  3% (1)
• D
  16% (5)

Explanation

Amazon S3 File Gateway (AWS Storage Gateway) exposes an on-premises NFS/SMB file share that durably stores files as S3 objects with local caching, enabling low-latency writes on-premises and asynchronous, near-real-time ingestion into Amazon S3 for analytics. It is purpose-built to "present a file interface backed by Amazon S3" and to "store files as objects in your S3 buckets," so existing applications writing to a network share can transparently land data in S3 without custom scripts or job orchestration. Compared with scheduled transfers (e.g., end-of-day DataSync), S3 File Gateway continuously uploads new/changed files, better meeting the near- real-time requirement. Transfer Family (SFTP) would require custom polling and client changes, increasing operational burden. DataSync is excellent for bulk or periodic migrations/synchronizations but is not as seamless for continuous ingestion from a live file share. Therefore, updating the application to point to an S3 File Gateway share provides the simplest, performant path to near-real-time delivery into S3 for downstream analytics.

No community discussion yet for this question.