AWS fsx documentation change
Summary
Updated networking service reference from 'AWS Direct Connect' to 'Direct Connect'
Security assessment
Minor branding change without security impact. Network peering architecture remains unchanged with no security implications.
Diff
diff --git a/fsx/latest/ONTAPGuide/create-flexcache.md b/fsx/latest/ONTAPGuide/create-flexcache.md index 5f5e218e3..5ae27e9dd 100644 --- a//fsx/latest/ONTAPGuide/create-flexcache.md +++ b//fsx/latest/ONTAPGuide/create-flexcache.md @@ -47 +47 @@ Before you begin using the procedures in the following sections, be sure that yo - * The source and destination file systems are connected in the same VPC, or are in networks that are peered using Amazon VPC, AWS Transit Gateway, AWS Direct Connect, or AWS VPN. For more information, see [Accessing data from within the AWS Cloud](./supported-fsx-clients.html#access-environments) 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 VPC, or are in networks that are peered using Amazon VPC, AWS Transit Gateway, Direct Connect, or AWS VPN. For more information, see [Accessing data from within the AWS Cloud](./supported-fsx-clients.html#access-environments) and [What is VPC peering?](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html) in the Amazon VPC Peering Guide.