Which solution will meet these requirements with the LEAST operational overhead?
Create an AWS Database Migration Service (AWS DMS) instance to replicate data from the storage of the vendors that use legacy applications to Amazon S3. Provide the vendors with the credentials to access the AWS DMS instance.
Create an AWS Transfer Family endpoint for vendors that use legacy applications.
Configure an Amazon EC2 instance to run an SFTP server. Instruct the vendors that use legacy applications to use the SFTP server to upload data.
Configure an Amazon S3 File Gateway for vendors that use legacy applications to upload files to an SMB file share.
Explanations:
AWS Database Migration Service (AWS DMS) is designed for migrating databases rather than handling file transfers. It would not provide a direct method for vendors to use SFTP to upload files to Amazon S3, thus adding unnecessary complexity and operational overhead.
AWS Transfer Family provides a fully managed service for transferring files over SFTP, FTPS, and FTP directly into and out of Amazon S3. This allows vendors using legacy applications to continue using SFTP without requiring changes to their systems, resulting in minimal operational overhead for the company.
Running an Amazon EC2 instance as an SFTP server would require significant operational overhead, including managing the server, handling scaling, security, and maintenance tasks. This option is not managed and would not be the least operationally intensive solution.
Amazon S3 File Gateway allows applications to access S3 storage through file interfaces like NFS and SMB. However, it does not support SFTP directly. This option would require additional configuration and may not fully meet the vendors’ needs for SFTP, leading to operational overhead.
I organize that the answer is:
Create an AWS Transfer Family endpoint for vendors that use legacy applications.
If I had to guess, I’d say the answer is:
Create an AWS Transfer Family endpoint for vendors that use legacy applications.