AWS Transfer Family supports custom ports for public SFTP servers

Published
October 12, 2026
https://aws.amazon.com/about-aws/whats-new/2026/10/transfer-family-custom-ports-sftp/

AWS Transfer Family Updates

AWS Transfer Family now allows you to configure custom ports on public SFTP servers and choose a communication mode for each port. This update enables you to support clients that require different ports or start SFTP connections differently on a single server.

Previously, public SFTP servers accepted connections only on port 22 and used server-first communication. Now, you can configure up to three ports (22, or any port from 2000 to 65535), allowing you to use the port numbers your business or network requires and offer multiple ports on one server. For each port, you can select client-first or server-first communication and direct clients to the port that matches their connection behavior. Using a port other than 22 can also reduce unwanted connection attempts from automated scanners that target port 22.

This capability is available in all AWS Regions where Transfer Family public SFTP servers are offered. To get started, visit the AWS Transfer Family console or use the AWS CLI or AWS SDKs.

What to do

  • Visit the AWS Transfer Family console or use the AWS CLI or AWS SDKs to configure custom ports and communication modes.
  • Choose up to three ports (22, or any port from 2000 to 65535) and select client-first or server-first communication for each port.
  • Direct clients to the port that matches their connection behavior to avoid connection stalls.
  • Use a port other than 22 to reduce unwanted connection attempts from automated scanners.

Source: AWS release notes




If you need further guidance on AWS, our experts are available at AWS@westloop.io. You may also reach us by submitting the Contact Us form.

Follow our blog

Get the latest insights and advice on AWS services from our experts.

By clicking Sign Up you're confirming that you agree with our Terms and Conditions.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.