AWS fsx: Add EFA client subnet/AZ and CIDR requirement for FSx Lustre
Summary
Adds a note that EFA clients must be in the same Availability Zone as the file system and that client and file system subnets must be in the same /16 CIDR range sharing the first two IPv4 octets.
Security assessment
Documents a network topology constraint (same AZ, same /16 CIDR) for EFA connectivity; it is configuration guidance with network-security relevance but does not fix a vulnerability or document a security feature.
Evidence
+The client must be in the same Availability Zone as your FSx for Lustre file system, and the client's subnet and the file system's subnet must be in the same `/16` Classless Inter-Domain Routing (CIDR) range. Their IPv4 addresses must share the same first two octets. For example, a client in subnet `10.24.34.0/24` can use EFA with a file system in subnet `10.24.56.0/24`, but not with one in `10.25.34.0/24`.
Diff
diff --git a/fsx/latest/LustreGuide/configure-efa-clients.md b/fsx/latest/LustreGuide/configure-efa-clients.md index f6abbe8..6947bfd 100644 --- a//fsx/latest/LustreGuide/configure-efa-clients.md +++ b//fsx/latest/LustreGuide/configure-efa-clients.md @@ -27,0 +28,2 @@ EFA is supported on Nitro v4 (or higher) EC2 instances that support EFA, excludi +The client must be in the same Availability Zone as your FSx for Lustre file system, and the client's subnet and the file system's subnet must be in the same `/16` Classless Inter-Domain Routing (CIDR) range. Their IPv4 addresses must share the same first two octets. For example, a client in subnet `10.24.34.0/24` can use EFA with a file system in subnet `10.24.56.0/24`, but not with one in `10.25.34.0/24`. +