Words By John Carl Villanueva
Last Updated:
To access AWS S3 via SFTP, configure the JSCAPE MFT Server by creating an Amazon S3 network storage object, entering AWS access and secret keys, and specifying the bucket and folder. Then, map this storage to a virtual path for SFTP to S3 file uploads, facilitating secure, direct SFTP access to S3 storage.
- Blog
- JSCAPE MFT
- Managed File Transfer
- Business Process Automation
SFTP is easily one of the most widely used file transfer protocols for business processes. Incidentally, Amazon S3 is also steadily becoming businesses' go-to cloud storage solution. How would you like to access AWS S3 via SFTP? If that looks like something you could use, check out this post. Would you prefer to watch a video showing how to access AWS S3 via SFTP? If so, you may play the video below. Otherwise, feel free to continue reading and if you'd like to learn more about JSCAPE MFT Server and how it can secure and manage your file transfers across thousands of users and multiple operating systems, schedule a demo with one of our experts. I have an Amazon S3 bucket named 'jscapejohn' and, inside that bucket, a folder named 'folder1'. Let's say I want SFTP file uploads to land in this folder. The SFTP server I'm using for this tutorial is JSCAPE MFT Server, a managed file transfer server that supports SFTP, along with several other file transfer protocols like FTP, FTPS, HTTP, HTTPS, AS2, OFTP, and many others. In addition to supporting a wide range of file transfer protocols, the JSCAPE MFT Server also supports several cloud storage and network services. So you can have your users and trading partners upload files via their file transfer protocol of choice and then have JSCAPE MFT Server store those files in your preferred cloud storage or network service. I'm now on my JSCAPE MFT Server instance, where I already have an SFTP service up and running. In order to store files uploaded through that SFTP service onto a folder in your Amazon S3 bucket, you need to create a corresponding Amazon S3 network storage object. Go to the Network Storage module and click the Add button to do that.Watch the video
Expand the Protocol drop-down list and select Amazon S3. Click OK to proceed.
Once the network storage parameters dialog appears, give this network storage a name, say, 'ns-s3'. After that, enter your AWS S3 access key and its corresponding secret key.
Next, specify the bucket and folder where you want your uploaded files to be stored.
You may test the connection between your JSCAPE MFT Server instance and your AWS S3 bucket by clicking the Test Server button. If you encounter an error like the one shown below, ...
...try checking the region associated with your AWS S3 bucket and see if it matches the region selected in the Region drop-down list. Change it if they don't match.
Click the Test Server button again. If the test succeeds, click OK until you're back at the main screen..
You should then see your newly created network storage object.
Now that you have an AWS S3 network storage object, the next step is to map it to a virtual path. There are two ways to do this. One is mapping it to a user's virtual path, and the other is mapping it to a group's virtual path. Let's map it to a user's virtual path for now.
Go to the Users module, select the user whose virtual path you want to map with your network storage object, and click Edit.
Navigate to the Paths tab and click the Add button to add a new virtual path.
Define the virtual path. For example, '/s3storage'. This means this virtual path will be located directly under this user account's root virtual path.
Next, map this virtual path to the network storage you created earlier by clicking the Network Storage option button and then selecting the AWS S3 network storage name from the drop-down list.
Click OK to proceed.
We're now ready to give this setup a test run. Let's connect to our SFTP service and see if we can find the AWS S3 virtual path there. Let me obtain the IP address of my JSCAPE MFT Server instance first.
So, in my SFTP client, I can enter that IP address into the appropriate field. I'm also going to enter the other pertinent details, like the username, password, port number of the SFTP service, and protocol type, which in this case is, of course, SFTP.
Note:I'm using the SFTP client for this example,JSCAPE AnyClient, a multi-protocol file transfer that supports SFTP and several other file transfer protocols.
As soon as I connect and log in using my file transfer client, I should see the folder 's3storage', which is the name of the virtual path that maps to my AWS S3 bucket folder.
So, if I upload files to this folder,
So, if I upload files to this folder, And check the actual S3 bucket folder in my AWS console, I should see the newly uploaded files there. Excited by the possibility of seamlessly integrating SFTP with AWS S3 for your secure file transfers? Book a demo with us today to explore how the JSCAPE MFT Server can streamline your file transfer processes and enhance your data security.
That's it. Now you know how to set up JSCAPE MFT Server, so your users can access AWS S3 via SFTP.
Try this yourself
Would you like to try this yourself? Download the FREE, fully functional Starter Edition of JSCAPE MFT Server now.
Download Now
Popular Articles
View more by JSCAPE
Setting Up SFTP Public Key Authentication On The Command Line
6min read —
SFTP Public Key Authentication enhances security by allowing users to access SFTP services without passwords, favoring automated transfers. The setup process involves creating a .ssh directory, generating a key pair with ssh-keygen, securing permissions, and copying the public key to the server, ensuring a secure connection without the need for passwords
Read ArticleActive vs. Passive FTP Simplified
7min read —
The difference between active FTP and passive FTP modes lies in how connections are made. In active mode, the client initiates the connection with a PORT command, making the server connect back for data. In passive mode, the client uses a PASV command, gets a server port, and starts the data transfer connection.
Read ArticleActive-Active vs. Active-Passive High-Availability Clustering
3min read —
An active-active high availability cluster distributes workloads evenly across all nodes, ensuring load balancing. An active-passive setup involves not all nodes being active, with the other node(s) on standby to take over if the active node fails, ensuring service continuity without load distribution.
Read Article
Posts By Category
Explore All Topics
- JSCAPE MFT
- Managed File Transfer
- Tutorials
- Secure File Transfer
- Business Process Automation
- Videos
- News
- SFTP
- Triggers
- FTP
- AS2
- FTPS
- File Transfer Clients
- Ad-Hoc File Transfers
- Reverse Proxy
- Accelerated File Transfer
- Case Studies
- sftp server
- file transfer
- ssh
- Client Certificate Authentication
- RSA 4096
- authentication
- encryption
- load balancing
- ASCII
- AWS
- Amazon S3
- Clustering
- Configuration
- DSA
- DSA vs RSA
- EDI
- FTP Server
- FTP command line
- FTP/S
- HMAC
- High Availability
- Load
- Load Balancer
- MDN
- OpenPGP keys
- RSA vs DSA
- S3
- SCP
- SMTP ports
- Transfer mode
- Windows SFTP Client
- binary mode
- binary transfer
- client certificate
- decrypt
- diffie-hellman-group1-sha1
- digital certificates
- file transfer protocol
- forward proxy
- ftp active mode
- ftp active vs passive
- ftp client
- ftp commands
- ftp passive mode
- ftp put command
- gnu privacy guard
- gpg
- key exchange
- key fingerprint
- mft gateway
- mft solutions
- passive ftp
- pgp
- port 25
- port 587
- proxy server
- reverse proxy server
- security
- sftp port
- sftp port number
- transfer protocols
- webdav
- webdav server
- windows ftp
Related Content
Read more about JSCAPE MFT
When SFTP isn’t enough— Signs you need an MFT Solution
19min read —
If SFTP limitations hinder your operations, consider an MFT solution for automation, protocol versatility, and advanced security. Explore our detailed blog post to learn when it's time to transition from SFTP to MFT and elevate your data transfers.
Read ArticleAS2 vs SFTP—What’s the difference?
22min read —
AS2, used for direct B2B exchanges like EDI over HTTP/S, emphasizes encryption, authentication, and non-repudiation with MDN receipts. SFTP, functioning over SSH, provides a secure method for broader file transfer needs, focusing on encryption, two-factor authentication, and integrity without inherent non-repudiation. Choose AS2 for specific B2B EDI requirements and SFTP for versatile, secure file sharing.
Read ArticleSFTP vs MFT: Choosing the Right File Transfer Protocol
18min read —
SFTP focuses on secure file transfers over a network with data encryption and authentication features. MFT, or Managed File Transfer, includes SFTP's security measures and offers comprehensive data security, automation, reporting, and compliance capabilities. MFT provides a more advanced solution for businesses by supporting multiple protocols while enhancing file transfer workflows with added security and efficiency.
Read Article
