AWS fsx documentation change
Summary
Updated references to 'AWS Direct Connect' and 'AWS CloudFormation' to use shorter service names ('Direct Connect' and 'CloudFormation') in multiple sections. No technical changes to content.
Security assessment
Changes are purely terminological adjustments (branding consistency) without altering security implications. The documentation continues to emphasize proper network configuration requirements but does not address new vulnerabilities or security features.
Diff
diff --git a/fsx/latest/ONTAPGuide/supported-fsx-clients.md b/fsx/latest/ONTAPGuide/supported-fsx-clients.md index aa5380cd8..db9bf7f34 100644 --- a//fsx/latest/ONTAPGuide/supported-fsx-clients.md +++ b//fsx/latest/ONTAPGuide/supported-fsx-clients.md @@ -142 +142 @@ Multi-AZ IPv4-only file systems created using the AWS CLI or Amazon FSx API use -Only [AWS Transit Gateway](https://aws.amazon.com/transit-gateway/?whats-new-cards.sort-by=item.additionalFields.postDateTime&whats-new-cards.sort-order=desc) supports routing to floating IP addresses, which is also known as transitive peering. VPC Peering, AWS Direct Connect, and AWS VPN don't support transitive peering. Therefore, you are required to use Transit Gateway in order to access these interfaces from networks that are outside of your file system's VPC. +Only [AWS Transit Gateway](https://aws.amazon.com/transit-gateway/?whats-new-cards.sort-by=item.additionalFields.postDateTime&whats-new-cards.sort-order=desc) supports routing to floating IP addresses, which is also known as transitive peering. VPC Peering, Direct Connect, and AWS VPN don't support transitive peering. Therefore, you are required to use Transit Gateway in order to access these interfaces from networks that are outside of your file system's VPC. @@ -154 +154 @@ For information about when you need to use Transit Gateway to access your FSx fo -Amazon FSx manages VPC route tables for Multi-AZ file systems using tag-based authentication. These route tables are tagged with `Key: AmazonFSx; Value: ManagedByAmazonFSx`. When creating or updating FSx for ONTAP Multi-AZ file systems using AWS CloudFormation we recommend that you add the `Key: AmazonFSx; Value: ManagedByAmazonFSx` tag manually. +Amazon FSx manages VPC route tables for Multi-AZ file systems using tag-based authentication. These route tables are tagged with `Key: AmazonFSx; Value: ManagedByAmazonFSx`. When creating or updating FSx for ONTAP Multi-AZ file systems using CloudFormation we recommend that you add the `Key: AmazonFSx; Value: ManagedByAmazonFSx` tag manually. @@ -160 +160 @@ The endpoints used to access FSx for ONTAP Single-AZ file systems over NFS or SM -The following diagram illustrates using AWS VPN or AWS Direct Connect for NFS, SMB, or management access to a Single-AZ file system that is in a different VPC than the clients accessing it. +The following diagram illustrates using AWS VPN or Direct Connect for NFS, SMB, or management access to a Single-AZ file system that is in a different VPC than the clients accessing it. @@ -162 +162 @@ The following diagram illustrates using AWS VPN or AWS Direct Connect for NFS, S - + @@ -189 +189 @@ You can use either VPC Peering or AWS Transit Gateway to access your file system -You can access your FSx for ONTAP file systems from on-premises using [AWS VPN](https://aws.amazon.com/vpn/) and [AWS Direct Connect](https://aws.amazon.com/getting-started/projects/connect-data-center-to-aws/); more specific use case guidelines are available in the following sections. In addition to any requirements listed below for accessing different FSx for ONTAP resources from on-premises, you also need to ensure that your file system's VPC security group allows data to flow between your file system and clients; for a list of required ports, see [Amazon VPC security groups](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/limit-access-security-groups.html#fsx-vpc-security-groups). +You can access your FSx for ONTAP file systems from on-premises using [AWS VPN](https://aws.amazon.com/vpn/) and [Direct Connect](https://aws.amazon.com/getting-started/projects/connect-data-center-to-aws/); more specific use case guidelines are available in the following sections. In addition to any requirements listed below for accessing different FSx for ONTAP resources from on-premises, you also need to ensure that your file system's VPC security group allows data to flow between your file system and clients; for a list of required ports, see [Amazon VPC security groups](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/limit-access-security-groups.html#fsx-vpc-security-groups). @@ -228 +228 @@ FSx for ONTAP’s inter-cluster endpoints are dedicated to replication traffic b -Because a file system's inter-cluster endpoints use IP addresses that are within the CIDR range of the VPC you provide when you create your FSx for ONTAP file system, you are not required to use a Transit Gateway for routing inter-cluster traffic between on-premises and the AWS Cloud. However, on-premises clients still must use AWS VPN or AWS Direct Connect to establish a secure connection to your VPC. +Because a file system's inter-cluster endpoints use IP addresses that are within the CIDR range of the VPC you provide when you create your FSx for ONTAP file system, you are not required to use a Transit Gateway for routing inter-cluster traffic between on-premises and the AWS Cloud. However, on-premises clients still must use AWS VPN or Direct Connect to establish a secure connection to your VPC.