AWS fsx documentation change
Summary
Updated terminology from 'AWS Direct Connect or AWS VPN' to 'Direct Connect or VPN' for consistency
Security assessment
Change involves branding/style updates rather than security content. No security implications - only adjusts service name references without altering access methods or security controls.
Diff
diff --git a/fsx/latest/LustreGuide/mounting-on-premises.md b/fsx/latest/LustreGuide/mounting-on-premises.md index 56f996435..7dd37b890 100644 --- a//fsx/latest/LustreGuide/mounting-on-premises.md +++ b//fsx/latest/LustreGuide/mounting-on-premises.md @@ -7 +7 @@ -You can access your Amazon FSx file system in two ways. One is from Amazon EC2 instances located in an Amazon VPC that's peered to the file system's VPC. The other is from on-premises clients that are connected to your file system's VPC using AWS Direct Connect or VPN. +You can access your Amazon FSx file system in two ways. One is from Amazon EC2 instances located in an Amazon VPC that's peered to the file system's VPC. The other is from on-premises clients that are connected to your file system's VPC using Direct Connect or VPN. @@ -30 +30 @@ Peered VPCs using VPC Peering or AWS Transit Gateway | Clients with IP addresses -Peered networks using AWS Direct Connect or AWS VPN | ✓ +Peered networks using Direct Connect or AWS VPN | ✓