AWS directconnect documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in titles and console references.
Security assessment
Purely branding/naming convention updates without any security context. No changes to security controls, vulnerabilities, or security-related procedures.
Diff
diff --git a/directconnect/latest/UserGuide/create-virtual-private-gateway.md b/directconnect/latest/UserGuide/create-virtual-private-gateway.md index abc5625b6..7105e82d8 100644 --- a//directconnect/latest/UserGuide/create-virtual-private-gateway.md +++ b//directconnect/latest/UserGuide/create-virtual-private-gateway.md @@ -5 +5 @@ -# Create an AWS Direct Connect virtual private gateway +# Create an Direct Connect virtual private gateway @@ -7 +7 @@ -The virtual private gateway must be attached to the VPC to which you want to connect. You can create a virtual private gateway and attach it to a VPC using either the AWS Direct Connect console or using the command line or API. +The virtual private gateway must be attached to the VPC to which you want to connect. You can create a virtual private gateway and attach it to a VPC using either the Direct Connect console or using the command line or API. @@ -17 +17 @@ After you create a virtual private gateway, you must attach it to your VPC. - 1. Open the **AWS Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). + 1. Open the **Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home).