AWS fsx documentation change
Summary
Updated network peering reference from 'AWS VPN' to 'Site-to-Site VPN'
Security assessment
Service name update without security configuration changes
Diff
diff --git a/fsx/latest/LustreGuide/migrating-fsx-lustre.md b/fsx/latest/LustreGuide/migrating-fsx-lustre.md index 1109dc51f..2d71a5354 100644 --- a//fsx/latest/LustreGuide/migrating-fsx-lustre.md +++ b//fsx/latest/LustreGuide/migrating-fsx-lustre.md @@ -21 +21 @@ To migrate data into your FSx for Lustre setup, you need a server and network th - * 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 [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 [What is VPC peering?](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html) in the _Amazon VPC Peering Guide_.