To configure AWS Transit Gateway for access to Multi-AZ file systems from on-premises
If you have a Multi-AZ file system with an EndpointIPAddressRange
that's outside your VPC's CIDR range, you need to set up additional routing
in your AWS Transit Gateway to access your file system from peered or on-premises networks.
Note
No additional Transit Gateway configuration is required for Single-AZ file systems
or Multi-AZ file systems with an EndpointIPAddressRange that's within
your VPC's IP address range.
Open the Amazon FSx console at https://console.aws.amazon.com/fsx/
. -
Choose the FSx for ONTAP file system for which you are configuring access from a peered network.
-
In Network & security copy the Endpoint IP address range.
-
Add a route to the Transit Gateway that routes traffic destined for this IP address range to your file system's VPC. For more information, see Work with transit gateways in the Amazon VPC Transit Gateway User Guide.
-
Confirm that you can access your FSx for ONTAP file system from the peered network.
Important
To access a Multi-AZ file system using a Transit Gateway, each of the Transit Gateway's attachments must be created in a subnet whose route table is associated with your file system.
To add a route table to your file system, see Updating file systems.
