AWS directconnect documentation change
Summary
Restructured content to reorganize resiliency models, removed 'Classic' model section, updated prerequisites, and simplified network requirement details. Added clarity about using the Connection Wizard and Classic connection alternatives.
Security assessment
Changes primarily involve content reorganization and terminology updates (e.g., removing standalone 'Classic' section, simplifying prerequisites). While previous versions mentioned security-adjacent network requirements like BGP MD5 authentication and VLAN encapsulation, these were removed as part of broader content simplification rather than addressing a specific security issue. No new security features or vulnerability mitigations were introduced.
Diff
diff --git a/directconnect/latest/UserGuide/resiliency_toolkit.md b/directconnect/latest/UserGuide/resiliency_toolkit.md index e96167ea0..0fb369133 100644 --- a//directconnect/latest/UserGuide/resiliency_toolkit.md +++ b//directconnect/latest/UserGuide/resiliency_toolkit.md @@ -5 +5 @@ -PrerequisitesMaximum resiliencyHigh resiliencyDevelopment and test ClassicFailover test +Available resiliency modelsAWS Direct Connect Resiliency Toolkit prerequisitesMaximum resiliencyHigh resiliencyDevelopment and test Failover test @@ -38,15 +37,0 @@ The AWS Direct Connect Resiliency Toolkit has the following benefits: -The following resiliency models are available in the AWS Direct Connect Resiliency Toolkit: - - * **Maximum Resiliency** : This model provides you a way to order dedicated connections to achieve an SLA of 99.99%. It requires you to meet all of the requirements for achieving the SLA that are specified in the [AWS Direct Connect Service Level Agreement](https://aws.amazon.com/directconnect/sla/). - - * **High Resiliency** : This model provides you a way to order dedicated connections to achieve an SLA of 99.9%. It requires you to meet all of the requirements for achieving the SLA that are specified in the [AWS Direct Connect Service Level Agreement](https://aws.amazon.com/directconnect/sla/). - - * **Development and Test** : This model provides you a way to achieve development and test resiliency for non-critical workloads, by using separate connections that terminate on separate devices in one location. - - * **Classic**. This model is intended for users that have existing connections and want to add additional connections. This model does not provide an SLA. - - - - -The best practice is to use the **Connection wizard** in the AWS Direct Connect Resiliency Toolkit to order the dedicated connections to achieve your SLA objective. - @@ -70,3 +55 @@ After you select the resiliency model, the AWS Direct Connect Resiliency Toolkit -## Prerequisites - -AWS Direct Connect supports the following port speeds over single-mode fiber: 1000BASE-LX (1310 nm) transceiver for 1 gigabit Ethernet, a 10GBASE-LR (1310 nm) transceiver for 10 gigabit, a 100GBASE-LR4 for 100 gigabit Ethernet, or a 400GBASE-LR4 for 400 Gbps Ethernet. +## Available resiliency models @@ -74,6 +57 @@ AWS Direct Connect supports the following port speeds over single-mode fiber: 10 -You can set up an AWS Direct Connect connection in one of the following ways: - -Model | Bandwidth | Method ----|---|--- -Dedicated connection | 1 Gbps, 10 Gbps, 100 Gbps, and 400 Gbps | Work with an AWS Direct Connect Partner or a network provider to connect a router from your data center, office, or colocation environment to an AWS Direct Connect location. The network provider does not have to be an [AWS Direct Connect Partner](https://aws.amazon.com/directconnect/partners) to connect you to a dedicated connection. AWS Direct Connect dedicated connections support these port speeds over single-mode fiber: 1 Gbps: 1000BASE-LX (1310 nm), 10 Gbps: 10GBASE-LR (1310 nm), 100Gbps: 100GBASE-LR4, or 400GBASE-LR4 for 400 Gbps Ethernet. -Hosted connection | 50 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, 10 Gbps, and 25 Gbps. | Work with a partner in the [AWS Direct Connect Partner Program](https://aws.amazon.com/directconnect/partners) to connect a router from your data center, office, or colocation environment to an AWS Direct Connect location. Only certain partners provide higher capacity connections. +The following resiliency models are available in the AWS Direct Connect Resiliency Toolkit: @@ -81 +59 @@ Hosted connection | 50 Mbps, 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1 -For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensure that your network meets the following requirements: + * **Maximum resiliency** : This model provides you a way to order dedicated connections to achieve an SLA of 99.99%. It requires you to meet all of the requirements for achieving the SLA that are specified in the [AWS Direct Connect Service Level Agreement](https://aws.amazon.com/directconnect/sla/). @@ -83 +61 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur - * Your network must use single-mode fiber with a 1000BASE-LX (1310 nm) transceiver for 1 gigabit Ethernet, a 10GBASE-LR (1310 nm) transceiver for 10 gigabit, a 100GBASE-LR4 for 100 gigabit Ethernet, or a 400GBASE-LR4 for 400 Gbps Ethernet. + * **High resiliency** : This model provides you a way to order dedicated connections to achieve an SLA of 99.9%. It requires you to meet all of the requirements for achieving the SLA that are specified in the [AWS Direct Connect Service Level Agreement](https://aws.amazon.com/directconnect/sla/). @@ -85 +63 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur - * Depending on the AWS Direct Connect endpoint serving your connection, on-premises device auto-negotiation might need to be enabled or disabled for any dedicated connection. If a virtual interface remains down when a Direct Connect connection is up, see [Troubleshooting layer 2 (data link) issues](./Troubleshooting.html#ts-layer-2). + * **Development and test** : This model provides you a way to achieve development and test resiliency for non-critical workloads, by using separate connections that terminate on separate devices in one location. @@ -87 +64,0 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur - * 802.1Q VLAN encapsulation must be supported across the entire connection, including intermediate devices. @@ -89 +65,0 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur - * Your device must support Border Gateway Protocol (BGP) and BGP MD5 authentication. @@ -91 +66,0 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur - * (Optional) You can configure Bidirectional Forwarding Detection (BFD) on your network. Asynchronous BFD is automatically enabled for each AWS Direct Connect virtual interface. It's automatically enabled for Direct Connect virtual interfaces, but does not take effect until you configure it on your router. For more information, see [Enable BFD for a Direct Connect connection](https://aws.amazon.com/premiumsupport/knowledge-center/enable-bfd-direct-connect/). @@ -92,0 +68 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur +The best practice is to use the **Connection wizard** in the AWS Direct Connect Resiliency Toolkit to order to achieve your SLA objective. @@ -93,0 +70 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur +###### Note @@ -94,0 +72 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur +If you do not want to create a resiliency model using the AWS Direct Connect Resiliency Toolkit, you can create a Classic connection. For more information about Classic connections, see [Classic connection](./classic_connection.html). @@ -96 +74 @@ For connections to AWS Direct Connect with bandwidths of 1 Gbps or higher, ensur -Make sure you have the following information before you begin your configuration: +## AWS Direct Connect Resiliency Toolkit prerequisites @@ -98 +76 @@ Make sure you have the following information before you begin your configuration - * The resiliency model that you want to use. +Note the following information before you begin your configuration: @@ -100 +78 @@ Make sure you have the following information before you begin your configuration - * The speed, location, and partner for all of your connections. + * Familiarize yourself with the [Connection prerequisites](./connection_options.html#connect-prereqs.title). @@ -102 +80 @@ Make sure you have the following information before you begin your configuration -You only need the speed for one connection. + * The available resiliency model that you want to use. @@ -131,25 +108,0 @@ For the procedure for using the AWS Direct Connect Resiliency Toolkit to configu -## Classic - -Select Classic when you have existing connections. - -The following procedures demonstrate the common scenarios to get set up with an AWS Direct Connect connection. - -### Prerequisites - -For connections to AWS Direct Connect with port speeds of 1 Gbps or higher, ensure that your network meets the following requirements: - - * Your network must use single-mode fiber with a 1000BASE-LX (1310 nm) transceiver for 1 gigabit Ethernet, a 10GBASE-LR (1310 nm) transceiver for 10 gigabit, a 100GBASE-LR4 for 100 gigabit Ethernet, or a 400GBASE-LR4 for 400 Gbps Ethernet. - - * Depending on the AWS Direct Connect endpoint serving your connection, on-premises device auto-negotiation might need to be enabled or disabled for any dedicated connection. If a virtual interface remains down when a Direct Connect connection is up, see [Troubleshooting layer 2 (data link) issues](./Troubleshooting.html#ts-layer-2). - - * 802.1Q VLAN encapsulation must be supported across the entire connection, including intermediate devices. - - * Your device must support Border Gateway Protocol (BGP) and BGP MD5 authentication. - - * (Optional) You can configure Bidirectional Forwarding Detection (BFD) on your network. Asynchronous BFD is automatically enabled for each AWS Direct Connect virtual interface. It's automatically enabled for Direct Connect virtual interfaces, but does not take effect until you configure it on your router. For more information, see [Enable BFD for a Direct Connect connection](https://aws.amazon.com/premiumsupport/knowledge-center/enable-bfd-direct-connect/). - - - - -For the procedure for using the AWS Direct Connect Resiliency Toolkit to configure a Classic connection, see [Configure a Classic connection](./toolkit-classic.html#configure-classic). - @@ -168 +121 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Private virtual interface routing example +Connection options