AWS fsx documentation change
Summary
Changed 'EndpointIpAddressRange' to lowercase 'endpoint IP address range' in documentation
Security assessment
Formatting/terminology clarification without functional changes or security implications. No security-related content added or modified.
Diff
diff --git a/fsx/latest/OpenZFSGuide/access-fsxopenzfs-onprem.md b/fsx/latest/OpenZFSGuide/access-fsxopenzfs-onprem.md index 7e9ba1f74..4928d7939 100644 --- a//fsx/latest/OpenZFSGuide/access-fsxopenzfs-onprem.md +++ b//fsx/latest/OpenZFSGuide/access-fsxopenzfs-onprem.md @@ -22 +22 @@ After you connect your on-premises environment to the VPC associated with your A -Amazon FSx requires that you use AWS Transit Gateway to access Multi-AZ file systems from an on-premises network. In order to support failover across AZs for Multi-AZ file systems, Amazon FSx uses floating IP addresses for the interfaces used for NFS endpoints. Because the NFS endpoints use floating IPs, you must use [AWS Transit Gateway](https://aws.amazon.com/transit-gateway/?whats-new-cards.sort-by=item.additionalFields.postDateTime&whats-new-cards.sort-order=desc) in conjunction with AWS Direct Connect or AWS VPN to access these interfaces from an on-premises network. The floating IP addresses used for these interfaces are within the `EndpointIpAddressRange` you specify when creating your Multi-AZ file system. By default, the Amazon FSx API selects a CIDR block of 16 available addresses from within the VPC's CIDR ranges. The floating IP addresses are used to enable a seamless transition of your clients to the standby file system in the event a failover is required. For more information, see [Failover process for FSx for OpenZFS](./availability-durability.html#multi-az-failover). +Amazon FSx requires that you use AWS Transit Gateway to access Multi-AZ file systems from an on-premises network. In order to support failover across AZs for Multi-AZ file systems, Amazon FSx uses floating IP addresses for the interfaces used for NFS endpoints. Because the NFS endpoints use floating IPs, you must use [AWS Transit Gateway](https://aws.amazon.com/transit-gateway/?whats-new-cards.sort-by=item.additionalFields.postDateTime&whats-new-cards.sort-order=desc) in conjunction with AWS Direct Connect or AWS VPN to access these interfaces from an on-premises network. The floating IP addresses used for these interfaces are within the endpoint IP address range you specify when creating your Multi-AZ file system. By default, the Amazon FSx API selects a CIDR block of 16 available addresses from within the VPC's CIDR ranges. The floating IP addresses are used to enable a seamless transition of your clients to the standby file system in the event a failover is required. For more information, see [Failover process for FSx for OpenZFS](./availability-durability.html#multi-az-failover). @@ -24 +24 @@ Amazon FSx requires that you use AWS Transit Gateway to access Multi-AZ file sys -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. For information, see [Configuring routing using AWS Transit Gateway](./access-within-aws.html#configuring-routing-using-AWSTG). +If you have a Multi-AZ file system with an endpoint IP address range 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. For information, see [Configuring routing using AWS Transit Gateway](./access-within-aws.html#configuring-routing-using-AWSTG).