AWS Security ChangesHomeSearch

AWS transfer: NLB/PPv2 guidance hardened against spoofed source IP bypass

Service: transfer · 2026-10-15 · Documentation medium

File: transfer/latest/userguide/working-with-nlb.md · Type: network

Summary

Rewrote NLB guidance to recommend avoiding an NLB where possible, scoped PPv2 to VPC-hosted endpoints, and added an explicit requirement to restrict the VPC endpoint security group to the trusted NLB so clients cannot bypass it and present a spoofed source IP.

Security assessment

The added text documents a concrete network-hardening control: because the server trusts the PPv2 source IP, the VPC endpoint security group must be locked to the NLB to prevent source-IP spoofing/bypass. This is security best-practice guidance rather than a fix for a named vulnerability or incident.

Evidence

+With `PROXY_PROTOCOL_V2_ENFORCED`, you must restrict the server's VPC endpoint security group to allow inbound traffic only through the trusted NLB. Because the server trusts the source IP address in the PPv2 header, this prevents a client from bypassing the NLB and presenting a spoofed source IP address.

Diff

diff --git a/transfer/latest/userguide/working-with-nlb.md b/transfer/latest/userguide/working-with-nlb.md
index 1d7820c..bbc93a6 100644
--- a//transfer/latest/userguide/working-with-nlb.md
+++ b//transfer/latest/userguide/working-with-nlb.md
@@ -11 +11 @@ Preserve the client's source IPEnable PPv2 enforcement
-Whether you can place a Network Load Balancer (NLB) in front of an AWS Transfer Family server depends on the protocol that your server uses. Review the following guidance before you add an NLB to your architecture.
+Whether you should place a Network Load Balancer (NLB) in front of an AWS Transfer Family server depends on the protocol that your server uses. Review the following guidance before you add an NLB to your architecture.
@@ -15 +15 @@ Whether you can place a Network Load Balancer (NLB) in front of an AWS Transfer
-  * **SFTP** – An NLB is supported. With PROXY protocol v2 (PPv2), you can preserve the client's source IP address on SFTP connections.
+  * **SFTP** – An NLB is supported for servers that use a VPC-hosted endpoint, though we recommend avoiding an NLB where possible. Where an NLB is required, you can preserve the client's source IP address with PROXY protocol v2 (PPv2).
@@ -20 +20 @@ Whether you can place a Network Load Balancer (NLB) in front of an AWS Transfer
-A common reason to place an NLB in front of an AWS Transfer Family server is to offer a custom listener port. AWS Transfer Family already offers several ports, so review [AWS Transfer Family endpoint type matrix](./sftp-for-transfer-family.html#endpoint-matrix) and [Create an SFTP-enabled server](./create-server-sftp.html) for the supported ports before you add an NLB.
+A common reason to place an NLB in front of an AWS Transfer Family server is to offer a custom listener port. AWS Transfer Family already offers several ports, so review [AWS Transfer Family endpoint type matrix](./sftp-for-transfer-family.html#endpoint-matrix) and [Create an SFTP-enabled server](./create-server-sftp.html) for the supported ports before you add an NLB to expose a custom listener port.
@@ -24 +24 @@ A common reason to place an NLB in front of an AWS Transfer Family server is to
-When an NLB is in the path between your client and your SFTP server, AWS Transfer Family sees the private IP address of the NLB instead of the client's source IP address. PROXY protocol v2 (PPv2) solves this problem. The NLB adds a PPv2 header that carries the client's source IP address, and AWS Transfer Family reads that header.
+This feature applies to SFTP servers that use a VPC-hosted endpoint. When an NLB is in the path between your client and your SFTP server, AWS Transfer Family sees the private IP address of the NLB instead of the client's source IP address. PROXY protocol v2 (PPv2) solves this problem. The NLB adds a PPv2 header that carries the client's source IP address, and AWS Transfer Family reads that header.
@@ -41 +41 @@ The `SftpMode` member of `ProxyConfig` controls how your server handles the PPv2
-With `PROXY_PROTOCOL_V2_ENFORCED` you must restrict the server's VPC endpoint security group to allow inbound traffic only via the trusted NLB.
+With `PROXY_PROTOCOL_V2_ENFORCED`, you must restrict the server's VPC endpoint security group to allow inbound traffic only through the trusted NLB. Because the server trusts the source IP address in the PPv2 header, this prevents a client from bypassing the NLB and presenting a spoofed source IP address.
@@ -47 +47 @@ Complete the following three steps in order to enable enforcement without refusi
-Enable the `proxy_protocol_v2.enabled` attribute on the NLB target group that points at your server's VPC endpoint. This attribute tells the NLB to prepend a PPv2 header to each connection. For instructions, see [Proxy protocol](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/edit-target-group-attributes.html#proxy-protocol) in the _Elastic Load Balancing User Guide_.
+Enable the `proxy_protocol_v2.enabled` attribute on the NLB target group that points at your server's VPC endpoint. This attribute tells the NLB to prepend a PPv2 header to each connection. For instructions, see [Proxy protocol for your Network Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/edit-target-group-attributes.html#proxy-protocol) in the _Elastic Load Balancing User Guide_.
@@ -53 +53 @@ While the server is still set to `SftpMode=NONE`, it reads and ignores any PPv2
-Before you enforce PPv2, confirm that the server receives a PPv2 header on every connection. Inspect your server logs for the `CONNECTED` activity type. In structured (JSON) logs in Amazon CloudWatch Logs, check the `proxy-protocol-v2-header` field for the value `ignored`; in legacy logs, check the `ProxyProtocolV2Header` field for the same value.
+Before you enforce PPv2, confirm that the server receives a PPv2 header on every connection. Inspect your server logs for the `CONNECTED` activity type. In structured (JSON) logs in Amazon CloudWatch Logs, check the `proxy-protocol-v2-header` field for the value `ignored`. In legacy logs, check the `ProxyProtocolV2Header` field for the same value.