AWS fsx documentation change
Summary
Replaced 'AWS VPN' with 'Site-to-Site VPN' terminology and updated related documentation references
Security assessment
The changes update product naming conventions to use official service names (Site-to-Site VPN). While VPN security is mentioned, this is existing documentation about secure connectivity methods rather than new security-related content or vulnerability fixes.
Diff
diff --git a/fsx/latest/OpenZFSGuide/access-fsxopenzfs-onprem.md b/fsx/latest/OpenZFSGuide/access-fsxopenzfs-onprem.md index e2a4ad639..976740187 100644 --- a//fsx/latest/OpenZFSGuide/access-fsxopenzfs-onprem.md +++ b//fsx/latest/OpenZFSGuide/access-fsxopenzfs-onprem.md @@ -9 +9 @@ Accessing Multi-AZ file systems -FSx for OpenZFS supports the use of AWS Direct Connect or AWS VPN to access your file systems from your on-premises compute instances. Using Direct Connect, you access your file system over a dedicated network connection from your on-premises environment. Using AWS VPN, you access your file system from your on-premises devices over a secure and private tunnel. +FSx for OpenZFS supports the use of AWS Direct Connect or Site-to-Site VPN to access your file systems from your on-premises compute instances. Using Direct Connect, you access your file system over a dedicated network connection from your on-premises environment. Using Site-to-Site VPN, you access your file system from your on-premises devices over a secure and private tunnel. @@ -11 +11 @@ FSx for OpenZFS supports the use of AWS Direct Connect or AWS VPN to access your -After you connect your on-premises environment to the VPC associated with your Amazon FSx file system, you can access your file system using its DNS name or a DNS alias. You do so just as you do from compute instances within the VPC. For more information about Direct Connect, see [What is AWS Direct Connect?](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) in the _Direct Connect User Guide_. For more information on setting up AWS VPN connections, see [VPN connections](https://docs.aws.amazon.com/vpc/latest/userguide/vpn-connections.html) in the _Amazon VPC User Guide_. +After you connect your on-premises environment to the VPC associated with your Amazon FSx file system, you can access your file system using its DNS name or a DNS alias. You do so just as you do from compute instances within the VPC. For more information about Direct Connect, see [What is AWS Direct Connect?](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) in the _Direct Connect User Guide_. For more information on setting up Site-to-Site VPN connections, see [VPN connections](https://docs.aws.amazon.com/vpc/latest/userguide/vpn-connections.html) in the _Amazon VPC User Guide_. @@ -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 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). +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 Site-to-Site 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).