AWS vpc documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in security context.
Security assessment
Terminology change in security section doesn't alter security guidance. Maintains existing security recommendations without additions.
Diff
diff --git a/vpc/latest/userguide/infrastructure-security.md b/vpc/latest/userguide/infrastructure-security.md index 4020f79d8..ba8c0ea3d 100644 --- a//vpc/latest/userguide/infrastructure-security.md +++ b//vpc/latest/userguide/infrastructure-security.md @@ -40 +40 @@ Consider the following options for controlling network traffic to the resources - * Use AWS Virtual Private Network or AWS Direct Connect to establish private connections from your remote networks to your VPCs. For more information, see [Network-to-Amazon VPC connectivity options](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/network-to-amazon-vpc-connectivity-options.html). + * Use AWS Virtual Private Network or Direct Connect to establish private connections from your remote networks to your VPCs. For more information, see [Network-to-Amazon VPC connectivity options](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/network-to-amazon-vpc-connectivity-options.html).