On the other hand, SFTP Gateway for AWS uploads files to the S3 location only when they are finished uploading to the server. You will then need to handle these in the S3 event listener. For SFTP clients that support partial file uploads, such as WinSCP and Filezilla, the S3 location will contain filepart files that will fire S3 events. The user does not have direct access to S3, but SFTP Gateway for AWS can be configured to provide more or less access to users.ĪWS SFTP directly uploads files to the S3 location. The downloads folder syncs its contents from a specified S3 location to provide access to files for a user. When a file is finished uploading, it is moved to S3 and deleted from the server. Users can then use SFTP to upload, download, and delete files to and from these buckets.īy default, SFTP Gateway for AWS provides an uploads folder and downloads folder for each user. Feature comparisons Access to S3 and S3 event behaviorsĪWS SFTP provides access to specific S3 buckets and prefixes per user.

Let’s go over some of these differences so you can determine which is the right fit for you.

While the two products are alike, there are certainly some important differences in how each product works, the features they have, and how much they cost. Of course it does – it’s very similar to our file transfer product, SFTP Gateway for AWS!īoth products use SSH to transfer files from your local environment into S3. AWS recently launched AWS Transfer for SFTP (or AWS SFTP, for short), a fully-managed service that transfers files into and out of Amazon S3 via SFTP.

Filezilla s3 amazon