AWS directconnect documentation change
Summary
Consolidated jumbo frames documentation for private and transit virtual interfaces under a single entry, standardizing MTU value to 9001 and removing transit-specific MTU 8500 details
Security assessment
The change unifies documentation but does not address security vulnerabilities. It clarifies MTU behavior without introducing or resolving security controls. The disruption mentioned (30s connectivity loss) is operational, not a security flaw.
Diff
diff --git a/directconnect/latest/UserGuide/hosted-vif.md b/directconnect/latest/UserGuide/hosted-vif.md index 47a8b08e8..3796e853f 100644 --- a//directconnect/latest/UserGuide/hosted-vif.md +++ b//directconnect/latest/UserGuide/hosted-vif.md @@ -53,2 +53 @@ For more information, see [Routing policies and BGP communities](https://docs.aw -(Private virtual interface 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. -(Transit virtual interface 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 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.