Which solution will meet these requirements with the LEAST administrative overhead?
Use AWS DataSync to transfer the files to Amazon S3. Create a scheduled task that runs at the end of each day.
Create an Amazon S3 File Gateway. Update the business system to use a new network share from the S3 File Gateway.
Use AWS DataSync to transfer the files to Amazon S3. Create an application that uses the DataSync API in the automation workflow.
Deploy an AWS Transfer for SFTP endpoint. Create a script that checks for new files on the network share and uploads the new files by using SFTP.
Explanations:
While AWS DataSync can transfer files to Amazon S3, creating a scheduled task that runs at the end of each day does not meet the near-real-time requirement and introduces additional administrative overhead for scheduling and monitoring.
An Amazon S3 File Gateway provides a seamless way to integrate on-premises applications with Amazon S3, allowing the business system to save reports directly to S3 without changing the existing workflow. This minimizes administrative overhead by removing the need for additional data transfer processes.
Using AWS DataSync with an application that utilizes the DataSync API introduces complexity and requires additional development and maintenance effort, which does not align with the requirement for the least administrative overhead.
Deploying an AWS Transfer for SFTP requires creating and managing an SFTP endpoint and a script to check for new files. This adds significant administrative overhead, making it less efficient than other options for near-real-time data transfer.