AWS directconnect documentation change
Summary
Updated documentation to replace 'AWS Direct Connect' with 'Direct Connect' throughout the text for consistency
Security assessment
The changes are purely branding/terminology updates without any security implications. No security vulnerabilities, mitigations, or security features were added or modified. The updates maintain the same technical content about virtual interface configuration requirements.
Diff
diff --git a/directconnect/latest/UserGuide/hosted-vif.md b/directconnect/latest/UserGuide/hosted-vif.md index f10db85b4..e93b3f626 100644 --- a//directconnect/latest/UserGuide/hosted-vif.md +++ b//directconnect/latest/UserGuide/hosted-vif.md @@ -5 +5 @@ -# Hosted AWS Direct Connect virtual interfaces +# Hosted Direct Connect virtual interfaces @@ -7 +7 @@ -To use your AWS Direct Connect connection with another account, you can create a hosted virtual interface for that account. The owner of the other account must accept the hosted virtual interface to begin using it. A hosted virtual interface works the same as a standard virtual interface and can connect to public resources or a VPC. +To use your Direct Connect connection with another account, you can create a hosted virtual interface for that account. The owner of the other account must accept the hosted virtual interface to begin using it. A hosted virtual interface works the same as a standard virtual interface and can connect to public resources or a VPC. @@ -15 +15 @@ Resource | Required information -**Connection** | The AWS Direct Connect connection or link aggregation group (LAG) for which you are creating the virtual interface. +**Connection** | The Direct Connect connection or link aggregation group (LAG) for which you are creating the virtual interface. @@ -19 +19 @@ Resource | Required information -**VLAN** | A unique virtual local area network (VLAN) tag that's not already in use on your connection. The value must be between 1 and 4094 and must comply with the Ethernet 802.1Q standard. This tag is required for any traffic traversing the AWS Direct Connect connection. If you have a hosted connection, your AWS Direct Connect Partner provides this value. You can’t modify the value after you have created the virtual interface. +**VLAN** | A unique virtual local area network (VLAN) tag that's not already in use on your connection. The value must be between 1 and 4094 and must comply with the Ethernet 802.1Q standard. This tag is required for any traffic traversing the Direct Connect connection. If you have a hosted connection, your AWS Direct Connect Partner provides this value. You can’t modify the value after you have created the virtual interface. @@ -45 +45 @@ We cannot guarantee that we will be able to fulfill all requests for AWS-provide - * IPv4: The IPv4 CIDR can overlap with another public IPv4 CIDR announced using AWS Direct Connect when either of the following is true: + * IPv4: The IPv4 CIDR can overlap with another public IPv4 CIDR announced using Direct Connect when either of the following is true: @@ -53 +53 @@ For more information, see [Routing policies and BGP communities](https://docs.aw -(Private and transit virtual interfaces only) **Jumbo frames** | The maximum transmission unit (MTU) of packets over AWS Direct Connect. The default is 1500. Setting the MTU of a virtual interface to 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all virtual interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from AWS Direct Connect. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the AWS Direct Connect console and find **Jumbo frame capable** on the virtual interface **General configuration** page. +(Private and transit virtual interfaces only) **Jumbo frames** | The maximum transmission unit (MTU) of packets over Direct Connect. The default is 1500. Setting the MTU of a virtual interface to 9001 (jumbo frames) can cause an update to the underlying physical connection if it wasn't updated to support jumbo frames. Updating the connection disrupts network connectivity for all virtual interfaces associated with the connection for up to 30 seconds. Jumbo frames apply only to propagated routes from Direct Connect. If you add static routes to a route table that point to your virtual private gateway, then traffic routed through the static routes is sent using 1500 MTU. To check whether a connection or virtual interface supports jumbo frames, select it in the Direct Connect console and find **Jumbo frame capable** on the virtual interface **General configuration** page.