AWS directconnect documentation change
Summary
Updated branding from 'AWS Direct Connect' to 'Direct Connect' throughout the document. Minor edits to terminology and links without changing technical functionality.
Security assessment
Changes are purely branding/terminology updates (e.g., 'AWS Direct Connect' → 'Direct Connect'). No modifications to security configurations, vulnerabilities, or security features. The MTU/jumbo frames section retains identical technical content with updated terminology.
Diff
diff --git a/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.md b/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.md index 26bf14788..cbd3bd20f 100644 --- a//directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.md +++ b//directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.md @@ -7 +7 @@ Public virtual interface prefix advertisement rulesSiteLinkPrerequisites for vir -# AWS Direct Connect virtual interfaces and hosted virtual interfaces +# Direct Connect virtual interfaces and hosted virtual interfaces @@ -9 +9 @@ Public virtual interface prefix advertisement rulesSiteLinkPrerequisites for vir -You must create one of the following virtual interfaces (VIFs) to begin using your AWS Direct Connect connection. +You must create one of the following virtual interfaces (VIFs) to begin using your Direct Connect connection. @@ -15 +15 @@ You must create one of the following virtual interfaces (VIFs) to begin using yo - * Transit virtual interface: A transit virtual interface should be used to access one or more Amazon VPC Transit Gateways associated with Direct Connect gateways. You can use transit virtual interfaces with any AWS Direct Connect dedicated or hosted connection of any speed. For information about Direct Connect gateway configurations, see [Direct Connect gateways](./direct-connect-gateways-intro.html). + * Transit virtual interface: A transit virtual interface should be used to access one or more Amazon VPC Transit Gateways associated with Direct Connect gateways. You can use transit virtual interfaces with any Direct Connect dedicated or hosted connection of any speed. For information about Direct Connect gateway configurations, see [Direct Connect gateways](./direct-connect-gateways-intro.html). @@ -45 +45 @@ If you're creating a private or transit virtual interface, you can use SiteLink. -SiteLink is an optional Direct Connect feature for private virtual interfaces that enables connectivity between any two Direct Connect points of presence (PoPs) in the same AWS partition using the shortest available path over the AWS network. This allows you to connect your on-premises network through the AWS global network without needing to route your traffic through a Region. For more information about SiteLink see [Introducing AWS Direct Connect SiteLink](https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-direct-connect-sitelink/). +SiteLink is an optional Direct Connect feature for private virtual interfaces that enables connectivity between any two Direct Connect points of presence (PoPs) in the same AWS partition using the shortest available path over the AWS network. This allows you to connect your on-premises network through the AWS global network without needing to route your traffic through a Region. For more information about SiteLink see [Introducing Direct Connect SiteLink](https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-direct-connect-sitelink/). @@ -87 +87 @@ 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. @@ -99 +99 @@ 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. @@ -130 +130 @@ The value can be one of the following: - * 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: @@ -138 +138 @@ 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 8500 (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 are supported up to 8500 MTU for Direct Connect. Static routes and propagated routes configured in the Transit Gateway Route Table will support Jumbo Frames, including from EC2 instances with VPC static route table entries to the Transit Gateway Attachment. 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 8500 (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 are supported up to 8500 MTU for Direct Connect. Static routes and propagated routes configured in the Transit Gateway Route Table will support Jumbo Frames, including from EC2 instances with VPC static route table entries to the Transit Gateway Attachment. 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. @@ -144 +144 @@ When you create a virtual interface, you can specify the account that owns the v - * For public VIFs, the account is used for virtual interface billing. The Data Transfer Out (DTO) usage is metered toward the resource owner at AWS Direct Connect data transfer rate. + * For public VIFs, the account is used for virtual interface billing. The Data Transfer Out (DTO) usage is metered toward the resource owner at Direct Connect data transfer rate. @@ -155 +155 @@ When you create a virtual interface, you can specify the account that owns the v -AWS Direct Connect supports an Ethernet frame size of 1522 or 9023 bytes (14 bytes Ethernet header + 4 bytes VLAN tag + bytes for the IP datagram + 4 bytes FCS) at the link layer. +Direct Connect supports an Ethernet frame size of 1522 or 9023 bytes (14 bytes Ethernet header + 4 bytes VLAN tag + bytes for the IP datagram + 4 bytes FCS) at the link layer. @@ -157 +157 @@ AWS Direct Connect supports an Ethernet frame size of 1522 or 9023 bytes (14 byt -The maximum transmission unit (MTU) of a network connection is the size, in bytes, of the largest permissible packet that can be passed over the connection. The MTU of a private virtual interface can be either 1500 or 9001 (jumbo frames). The MTU of a transit virtual interface can be either 1500 or 8500 (jumbo frames). You can specify the MTU when you create the interface or update it after you create it. Setting the MTU of a virtual interface to 8500 (jumbo frames) or 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. 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 **Summary** tab. +The maximum transmission unit (MTU) of a network connection is the size, in bytes, of the largest permissible packet that can be passed over the connection. The MTU of a private virtual interface can be either 1500 or 9001 (jumbo frames). The MTU of a transit virtual interface can be either 1500 or 8500 (jumbo frames). You can specify the MTU when you create the interface or update it after you create it. Setting the MTU of a virtual interface to 8500 (jumbo frames) or 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. 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 **Summary** tab. @@ -163 +163 @@ After you enable jumbo frames for your private virtual interface or transit virt -Jumbo frames will apply only to propagated routes via AWS Direct Connect and static routes via transit gateways. Jumbo frames on transit gateways support only 8500 bytes. +Jumbo frames will apply only to propagated routes via Direct Connect and static routes via transit gateways. Jumbo frames on transit gateways support only 8500 bytes.