Google Shared Drive and Workspace SFTP and FTP
Moving into the cloud often means sacrificing features and functionality, in this case the weigh up of continuing to host an on-premises secure FTP server, or spinning up a dedicated node in your cloud infrastructure. This often leads to the question, do I want to open up my infrastructure for public access?
Just because you are transferring into the likes of Google Drive or SharePoint doesn’t mean that you have to make such sacrifices, especially when SFTP is not going anywhere and is in fact growing across all industries, finance, health, marketing companies and logistics to name a few. This is where Couchdrop a secure file gateway or cloud SFTP server can assist.
Couchdrop acts as a comprehensive SFTP server in the cloud, that is fully managed and sits as a gateway into your Google Shared Drive, SharePoint, S3 bucket or another platform. It provides granular security functionality such as IP whitelisting, 2FA, RSA keys, as well enterprise audit logging, file workflows and automation (conduct actions on files based on certain events or conditions) and other access methods (FTP, SCP, Rsync, HTTPS, S3, etc.).
However if you are looking for a simple and secure replacement for your current on-premise, or cloud, SFTP server then look no further. Couchdrop will enable your clients to interact directly with data on a Google Workspace Shared Drive through SFTP or FTP, all without Couchdrop storing a single file.
How to configure SFTP for Shared Drives
Trust us, you’ll be up and running in less than 5 minutes.
Step 1: Create a Couchdrop account (free 14-day trial, no credit card required)
Step 2: Configure your Google Shared Drive by delegating domain API access
Complete guide here on how to configure a Google Shared Drive with Couchdrop. You’re best to add your Shared Drive as a subpath to the mount point.
Step 3: Configure users to access specific folders within your Shared Drive
You can lock users down to specific file operations and folders within a Google Shared Drive and also deny access to insecure protocols such as FTP.
Step 4. Start receiving files via SFTP, FTP or FTP/S
Using your organisation subdomain (when you registered your account) or point a CNAME to this, you can use the credentials created to interact with your Shared Drive via SFTP, FTP or whatever protocol you require (even an upload portal).