AWS transfer: Document editing SFTP custom ports and OFFLINE requirement
Summary
Adds documentation for configuring SFTP custom ports on a PUBLIC endpoint server via SftpPorts, including CommunicationMode options, and notes the server must be OFFLINE to change the ports.
Security assessment
Documents a network configuration option (listening ports) and an operational prerequisite (server must be OFFLINE). No security feature, hardening guidance, or vulnerability is described, so it is only tangentially security-relevant via network exposure.
Evidence
+To change the SFTP custom ports, your server must be in the OFFLINE state. To stop your server, see Put your server online or offline.
Diff
diff --git a/transfer/latest/userguide/edit-server-config.md b/transfer/latest/userguide/edit-server-config.md index ec51847..ba81c46 100644 --- a//transfer/latest/userguide/edit-server-config.md +++ b//transfer/latest/userguide/edit-server-config.md @@ -77,0 +78,6 @@ Avoid placing Network Load Balancers (NLBs) or NAT gateways in front of AWS Tran + * **SFTP custom ports** : For an SFTP server that uses a `PUBLIC` endpoint type, 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. You set these options when you create or update a server. For more information, see the `SftpPorts` documentation in the [ProtocolDetails](https://docs.aws.amazon.com/transfer/latest/APIReference/API_ProtocolDetails.html) topic. + +###### Note + +To change the SFTP custom ports, your server must be in the OFFLINE state. To stop your server, see Put your server online or offline. +