AWS fsx documentation change
Summary
Updated VPN terminology from 'AWS VPN' to 'Site-to-Site VPN'
Security assessment
Terminology update for consistency. No security implications as the change describes the same networking concept with updated branding.
Diff
diff --git a/fsx/latest/OpenZFSGuide/migrating-fsx-openzfs.md b/fsx/latest/OpenZFSGuide/migrating-fsx-openzfs.md index 8df31ad56..8852494de 100644 --- a//fsx/latest/OpenZFSGuide/migrating-fsx-openzfs.md +++ b//fsx/latest/OpenZFSGuide/migrating-fsx-openzfs.md @@ -22 +22 @@ Before you begin using the procedures described in the following sections, be su - * The source and destination file systems are connected in the same virtual private cloud (VPC). The source file system can be located on-premises or in another Amazon VPC, AWS account, or AWS Region, but it must be in a network peered with that of the destination file system using Amazon VPC Peering, Transit Gateway, AWS Direct Connect, or AWS VPN. For more information, see [Access from a different VPC](./access-within-aws.html#vpc-peering) and [What is VPC peering?](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html) in the _Amazon VPC Peering Guide_. + * The source and destination file systems are connected in the same virtual private cloud (VPC). The source file system can be located on-premises or in another Amazon VPC, AWS account, or AWS Region, but it must be in a network peered with that of the destination file system using Amazon VPC Peering, Transit Gateway, AWS Direct Connect, or Site-to-Site VPN. For more information, see [Access from a different VPC](./access-within-aws.html#vpc-peering) and [What is VPC peering?](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html) in the _Amazon VPC Peering Guide_.