AWS directconnect documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in headings and content
Security assessment
Standard branding updates without technical changes to security configurations or guidance. No evidence of security impact.
Diff
diff --git a/directconnect/latest/UserGuide/virtualgateways.md b/directconnect/latest/UserGuide/virtualgateways.md index 47f0ffeaa..a134ecc2d 100644 --- a//directconnect/latest/UserGuide/virtualgateways.md +++ b//directconnect/latest/UserGuide/virtualgateways.md @@ -5 +5 @@ -# AWS Direct Connect virtual private gateway associations +# Direct Connect virtual private gateway associations @@ -7 +7 @@ -You can associate a virtual private gateway with a Direct Connect gateway to enable connectivity between your AWS Direct Connect connection and VPCs across different accounts and Regions. Each VPC requires a virtual private gateway that you associate with the Direct Connect gateway. Once these associations are established, you create private virtual interfaces on your Direct Connect connection to the Direct Connect gateway, allowing multiple VPCs to share the same Direct Connect connection through their respective virtual private gateway associations.. +You can associate a virtual private gateway with a Direct Connect gateway to enable connectivity between your Direct Connect connection and VPCs across different accounts and Regions. Each VPC requires a virtual private gateway that you associate with the Direct Connect gateway. Once these associations are established, you create private virtual interfaces on your Direct Connect connection to the Direct Connect gateway, allowing multiple VPCs to share the same Direct Connect connection through their respective virtual private gateway associations.. @@ -46 +46 @@ The following rules apply to virtual private gateway associations: -To connect your AWS Direct Connect connection to a VPC in the same Region only, you can create a Direct Connect gateway. Or, you can create a private virtual interface and attach it to the virtual private gateway for the VPC. For more information, see [Create a private virtual interface](./create-private-vif.html) and [VPN CloudHub](https://docs.aws.amazon.com/vpc/latest/userguide/VPN_CloudHub.html). +To connect your Direct Connect connection to a VPC in the same Region only, you can create a Direct Connect gateway. Or, you can create a private virtual interface and attach it to the virtual private gateway for the VPC. For more information, see [Create a private virtual interface](./create-private-vif.html) and [VPN CloudHub](https://docs.aws.amazon.com/vpc/latest/userguide/VPN_CloudHub.html). @@ -48 +48 @@ To connect your AWS Direct Connect connection to a VPC in the same Region only, -To use your AWS Direct Connect connection with a VPC in another account, you can create a hosted private virtual interface for that account. When the owner of the other account accepts the hosted virtual interface, they can choose to attach it either to a virtual private gateway or to a Direct Connect gateway in their account. For more information, see [Virtual interfaces and hosted virtual interfaces](./WorkingWithVirtualInterfaces.html). +To use your Direct Connect connection with a VPC in another account, you can create a hosted private virtual interface for that account. When the owner of the other account accepts the hosted virtual interface, they can choose to attach it either to a virtual private gateway or to a Direct Connect gateway in their account. For more information, see [Virtual interfaces and hosted virtual interfaces](./WorkingWithVirtualInterfaces.html).