AWS transfer: Document SFTP custom ports for public endpoint servers
Summary
Adds documentation for the SftpPorts property, which lets an SFTP server with a PUBLIC endpoint listen on up to three configurable ports (2000-65535 or 22) with a CommunicationMode setting.
Security assessment
The change documents a new network configuration capability (listening ports on a public endpoint) rather than a security feature or best practice. It has network-exposure implications but no security guidance, hardening advice, or vulnerability reference is provided.
Evidence
+ * **SFTP custom ports** : For an SFTP server that uses a `PUBLIC` endpoint, you can choose the ports that the server listens on.
Diff
diff --git a/transfer/latest/userguide/create-server-sftp.md b/transfer/latest/userguide/create-server-sftp.md index 154a2f2..f2b6024 100644 --- a//transfer/latest/userguide/create-server-sftp.md +++ b//transfer/latest/userguide/create-server-sftp.md @@ -132,0 +133,2 @@ When you create your server using the console, optimized directories is enabled + * **SFTP custom ports** : For an SFTP server that uses a `PUBLIC` endpoint, you can choose the ports that the server listens on. Use the `SftpPorts` property to configure up to three ports. Each port can be any integer from 2000 to 65535, or 22. For each port, you can also set a `CommunicationMode` that controls which side sends data first. Use `CLIENT_TALK_FIRST` for clients that require TCP piggy-back ACKs. A piggy-back ACK carries data in the final ACK of the TCP three-way handshake. Use `SERVER_TALK_FIRST` if you are unsure of your clients' behavior or your clients do not depend on this. For more information, see the `SftpPorts` documentation in the [ProtocolDetails](https://docs.aws.amazon.com/transfer/latest/APIReference/API_ProtocolDetails.html) topic. +