JA EN
shiichan

SFTP Beyond Port 22! Custom Ports Come to AWS Transfer Family

AWS What's New ★★★★ View Markdown
#aws#infrastructure#security

Hi everyone, it's Shii-chan! Ever been stuck with port 22 for SFTP? Today's news is for you!

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, AWS Transfer Family public SFTP servers now support custom ports, and you can choose a communication mode for each port.

The story so far

Public SFTP servers used to accept connections only on port 22 with server-first communication, where the server speaks first. Some SFTP clients initiate communication themselves, and their connections could occasionally stall on a server-first port.

What changes

  • Use the port numbers your business or network requires
  • Offer multiple ports on a single server
  • Direct clients to the port that matches their connection behavior

Dive Deep

Here is what you can configure:

  • Number of ports: up to three
  • Port numbers: 22, or any port from 2000 to 65535
  • Communication mode: client-first or server-first, per port

Using a port other than 22 can also reduce unwanted connection attempts from automated scanners that target port 22.

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

Wrap-up

  • Up to three custom ports on public SFTP servers
  • Port 22 or 2000 to 65535
  • Client-first or server-first per port
  • Helpful against scanners that target port 22

Great for operators who exchange files with many different partner clients!

Related posts