AWS fsx documentation change
Summary
Updated networking documentation to use 'Site-to-Site VPN' terminology instead of 'AWS VPN'
Security assessment
This is a terminology standardization change clarifying VPN service naming. The security context around transitive peering requirements remains unchanged, with no new security features or vulnerabilities addressed.
Diff
diff --git a/fsx/latest/OpenZFSGuide/access-within-aws.md b/fsx/latest/OpenZFSGuide/access-within-aws.md index 7914169dc..051737a37 100644 --- a//fsx/latest/OpenZFSGuide/access-within-aws.md +++ b//fsx/latest/OpenZFSGuide/access-within-aws.md @@ -48 +48 @@ When you create a file system, you can optionally specify the endpoint IP addres -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. +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 Site-to-Site 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.