Amazon FSx for NetApp ONTAP file systems are reachable only through the VPC in which their ENIs reside or through a peering connection that extends the VPC’s private address space.

The service documentation explicitly states that clients in another VPC must use an active VPC-peering relationship (and matching route/security-group rules) to mount NFS/CIFS exports. Transit Gateway, Direct Connect Gateway, or deploying a second FSx instance are not required for—nor explicitly supported by—simple VPC-to-VPC access of a single file system.

B. Transit Gateway is not listed as a supported access path for FSx for ONTAP; VPC peering is the prescribed method for inter-VPC client access.

C. Duplicating the file system is unnecessary; networking, not storage placement, is the issue.

D. Direct Connect Gateway enables on-premises to VPC connectivity, not traffic exchange between two AWS VPCs.

1. AWS, “Amazon FSx for NetApp ONTAP – Accessing from Peered VPCs,” User Guide, § “Prerequisites,” bullet 1 (2023-10-12).

2. AWS, “Amazon FSx for NetApp ONTAP – Networking & Security,” User Guide, § “VPC Peering Support,” para 1-2 (2023-10-12).

3. AWS, “AWS Direct Connect – Direct Connect Gateway,” Developer Guide, § “Use cases,” lists only on-premises to multiple VPCs (2023-09).