Skip to main content
AWS Transfer Family provides managed SFTP, FTPS, and FTP endpoints for transferring files into and out of Amazon S3 or EFS. There’s no separate AWS Transfer Family connector in Integrate.io: since Transfer Family exposes a standard SFTP endpoint, you connect to it using Integrate.io’s regular SFTP connector (found under File Stores), pointed at your Transfer Family server’s hostname. This guide walks through that setup.

​
Prerequisites

  • An Integrate.io account with permissions to create connections
  • An AWS Transfer Family server already provisioned, with SFTP enabled
  • The server’s hostname/endpoint
  • A username, and a password and/or SSH key pair, depending on how your Transfer Family server is configured for authentication

​
Connecting to your AWS Transfer Family server

1
In the Integrate.io dashboard, go to Connections (lightning bolt icon) → New Connection, then search for and select Secure File Transfer Protocol (SFTP) under File Stores.
2
Enter a descriptive name (e.g., “AWS Transfer Family - Production”) in the Name field. Maximum 512 characters.
3
Under Access type, choose based on how your Transfer Family server is reachable:
  • Direct connection: use this if your Transfer Family server has a public endpoint. You’ll need to whitelist Integrate.io’s IP addresses for this to work.
  • SSH tunnel connection: use this if your Transfer Family server sits inside a private VPC and you’re tunneling through a bastion/jump host.
  • Reverse SSH tunnel connection: use this if your network setup requires the tunnel to be initiated from your side rather than Integrate.io’s.
Most Transfer Family setups with a public endpoint use Direct connection. If your server is VPC-internal only, check with whoever manages your AWS networking on which tunnel option applies.
4
Enter the connection details:
  • Hostname: your AWS Transfer Family server’s endpoint (found in the AWS Transfer Family console under your server’s details)
  • Port: 22 (default, matches AWS Transfer Family’s standard SFTP port)
5
Under Authentication method, select the option matching how your Transfer Family user is configured:
  • Password authentication: enter the User name and Password for your Transfer Family user.
  • Public key authentication: enter the User name and provide Integrate.io’s public key to add to your Transfer Family user’s authorized keys in AWS.
  • Private key + password authentication: combines both, if your Transfer Family server requires key-based auth alongside a password/passphrase.
Username and password (or key) fields cannot be left blank. The form flags this before allowing you to proceed.
6
If you selected Direct connection, whitelist Integrate.io’s IP addresses in your Transfer Family server’s associated security group or network configuration before testing. Integrate.io’s current IP list is available in the connection documentation. This step doesn’t apply if you’re using an SSH tunnel or reverse SSH tunnel connection.
7
Click Test connection to confirm Integrate.io can reach your Transfer Family server. Once successful, click Create Connection.

​
Troubleshooting

Usually means Integrate.io’s IPs haven’t been whitelisted yet on the AWS security group, or the Transfer Family server isn’t publicly reachable. Confirm whether your server actually needs a tunnel connection instead.
Double-check the username/password or key matches exactly what’s configured for your Transfer Family user, and confirm the authentication method selected matches how that user is set up in AWS.
These are required fields. The form won’t let you create the connection until they’re filled in.
Last modified on September 23, 2026