AWS Security ChangesHomeSearch

AWS fsx documentation change

Service: fsx · 2025-11-19 · Documentation low

File: fsx/latest/OpenZFSGuide/access-within-aws.md

Summary

Updated 'AWS Direct Connect' to 'Direct Connect' in transitive peering documentation

Security assessment

Minor terminology adjustment without changing security implications of transitive peering requirements. Network security guidance remains consistent.

Diff

diff --git a/fsx/latest/OpenZFSGuide/access-within-aws.md b/fsx/latest/OpenZFSGuide/access-within-aws.md
index 9f07be3c4..7914169dc 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, 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.