AWS directconnect documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' throughout the documentation for consistency in branding/terminology. No functional changes to procedures or configurations.
Security assessment
The changes are purely branding/naming convention updates (removing 'AWS' from service name references). There is no evidence of addressing security vulnerabilities, modifying security controls, or introducing new security features. The documentation updates do not impact security configurations or best practices.
Diff
diff --git a/directconnect/latest/UserGuide/toolkit-classic.md b/directconnect/latest/UserGuide/toolkit-classic.md index 6c209d320..d7b93d630 100644 --- a//directconnect/latest/UserGuide/toolkit-classic.md +++ b//directconnect/latest/UserGuide/toolkit-classic.md @@ -5 +5 @@ -Step 1: Sign up for AWSStep 2: Request an AWS Direct Connect dedicated connection(Dedicated connection) Step 3: Download the LOA-CFAStep 4: Create a virtual interfaceStep 5: Download the router configurationStep 6: Verify your virtual interface(Recommended) Step 7: Configure redundant connections +Step 1: Sign up for AWSStep 2: Request an Direct Connect dedicated connection(Dedicated connection) Step 3: Download the LOA-CFAStep 4: Create a virtual interfaceStep 5: Download the router configurationStep 6: Verify your virtual interface(Recommended) Step 7: Configure redundant connections @@ -7 +7 @@ Step 1: Sign up for AWSStep 2: Request an AWS Direct Connect dedicated connectio -# Configure an AWS Direct Connect Classic connection +# Configure an Direct Connect Classic connection @@ -13 +13 @@ Configure a Classic connection when you have existing Direct Connect connections -To use AWS Direct Connect, you need an account if you don't already have one. +To use Direct Connect, you need an account if you don't already have one. @@ -86 +86 @@ For instructions, see [ Add groups](https://docs.aws.amazon.com/singlesignon/lat -## Step 2: Request an AWS Direct Connect dedicated connection +## Step 2: Request an Direct Connect dedicated connection @@ -88 +88 @@ For instructions, see [ Add groups](https://docs.aws.amazon.com/singlesignon/lat -For dedicated connections, you can submit a connection request using the AWS Direct Connect console. For hosted connections, work with an AWS Direct Connect Partner to request a hosted connection. Ensure that you have the following information: +For dedicated connections, you can submit a connection request using the Direct Connect console. For hosted connections, work with an AWS Direct Connect Partner to request a hosted connection. Ensure that you have the following information: @@ -92 +92 @@ For dedicated connections, you can submit a connection request using the AWS Dir - * The AWS Direct Connect location at which the connection is to be terminated. + * The Direct Connect location at which the connection is to be terminated. @@ -99 +99 @@ For dedicated connections, you can submit a connection request using the AWS Dir -You cannot use the AWS Direct Connect console to request a hosted connection. Instead, contact an AWS Direct Connect Partner, who can create a hosted connection for you, which you then accept. Skip the following procedure and go to Accept your hosted connection. +You cannot use the Direct Connect console to request a hosted connection. Instead, contact an AWS Direct Connect Partner, who can create a hosted connection for you, which you then accept. Skip the following procedure and go to Accept your hosted connection. @@ -101 +101 @@ You cannot use the AWS Direct Connect console to request a hosted connection. In -###### To create a new AWS Direct Connect connection +###### To create a new Direct Connect connection @@ -103 +103 @@ You cannot use the AWS Direct Connect console to request a hosted connection. In - 1. Open the **AWS Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). + 1. Open the **Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). @@ -113 +113 @@ You cannot use the AWS Direct Connect console to request a hosted connection. In - 2. For **Location** , select the appropriate AWS Direct Connect location. + 2. For **Location** , select the appropriate Direct Connect location. @@ -119 +119 @@ You cannot use the AWS Direct Connect console to request a hosted connection. In - 5. For **On-premises** , select **Connect through an AWS Direct Connect partner** when you use this connection to connect to your data center. + 5. For **On-premises** , select **Connect through an Direct Connect partner** when you use this connection to connect to your data center. @@ -142 +142 @@ It can take up to 72 business hours for AWS to review your request and provision -For more information, see [AWS Direct Connect dedicated and hosted connections](./WorkingWithConnections.html). +For more information, see [Direct Connect dedicated and hosted connections](./WorkingWithConnections.html). @@ -146 +146 @@ For more information, see [AWS Direct Connect dedicated and hosted connections]( -You must accept the hosted connection in the AWS Direct Connect console before you can create a virtual interface. This step only applies to hosted connections. +You must accept the hosted connection in the Direct Connect console before you can create a virtual interface. This step only applies to hosted connections. @@ -150 +150 @@ You must accept the hosted connection in the AWS Direct Connect console before y - 1. Open the **AWS Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). + 1. Open the **Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). @@ -167 +167 @@ After you request a connection, we make a Letter of Authorization and Connecting - 1. Open the **AWS Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). + 1. Open the **Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). @@ -183 +183 @@ If the link is not enabled, the LOA-CFA is not yet available for you to download - * If you're working with an AWS Direct Connect Partner or network provider, send them the LOA-CFA so that they can order a cross-connect for you at the AWS Direct Connect location. If they cannot order the cross-connect for you, you can [contact the colocation provider](./Colocation.html) directly. + * If you're working with an AWS Direct Connect Partner or network provider, send them the LOA-CFA so that they can order a cross-connect for you at the Direct Connect location. If they cannot order the cross-connect for you, you can [contact the colocation provider](./Colocation.html) directly. @@ -185 +185 @@ If the link is not enabled, the LOA-CFA is not yet available for you to download - * If you have equipment at the AWS Direct Connect location, contact the colocation provider to request a cross-network connection. You must be a customer of the colocation provider. You must also present them with the LOA-CFA that authorizes the connection to the AWS router, and the necessary information to connect to your network. + * If you have equipment at the Direct Connect location, contact the colocation provider to request a cross-network connection. You must be a customer of the colocation provider. You must also present them with the LOA-CFA that authorizes the connection to the AWS router, and the necessary information to connect to your network. @@ -190 +190 @@ If the link is not enabled, the LOA-CFA is not yet available for you to download -AWS Direct Connect locations that are listed as multiple sites (for example, Equinix DC1-DC6 & DC10-DC11) are set up as a campus. If your or your network provider’s equipment is located in any of these sites, you can request a cross-connect to your assigned port even if it resides in a different campus building. +Direct Connect locations that are listed as multiple sites (for example, Equinix DC1-DC6 & DC10-DC11) are set up as a campus. If your or your network provider’s equipment is located in any of these sites, you can request a cross-connect to your assigned port even if it resides in a different campus building. @@ -194 +194 @@ AWS Direct Connect locations that are listed as multiple sites (for example, Equ -A campus is treated as a single AWS Direct Connect location. To achieve high availability, configure connections to different AWS Direct Connect locations. +A campus is treated as a single Direct Connect location. To achieve high availability, configure connections to different Direct Connect locations. @@ -200 +200 @@ If you or your network provider experience issues establishing a physical connec -To begin using your AWS Direct Connect connection, you must create a virtual interface. You can create a private virtual interface to connect to your VPC. Or, you can create a public virtual interface to connect to public AWS services that aren't in a VPC. When you create a private virtual interface to a VPC, you need a private virtual interface for each VPC to which to connect. For example, you need three private virtual interfaces to connect to three VPCs. +To begin using your Direct Connect connection, you must create a virtual interface. You can create a private virtual interface to connect to your VPC. Or, you can create a public virtual interface to connect to public AWS services that aren't in a VPC. When you create a private virtual interface to a VPC, you need a private virtual interface for each VPC to which to connect. For example, you need three private virtual interfaces to connect to three VPCs. @@ -206 +206 @@ 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. @@ -210 +210 @@ 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. @@ -236 +236 @@ 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: @@ -244 +244 @@ 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. @@ -248 +248 @@ We request additional information from you if your public prefixes or ASNs belon -For private virtual interface and public virtual interfaces, 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. +For private virtual interface and public virtual interfaces, 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. @@ -254 +254 @@ When you create a public virtual interface, it can take up to 72 business hours - 1. Open the **AWS Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). + 1. Open the **Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). @@ -270 +270 @@ When you create a public virtual interface, it can take up to 72 business hours - 4. For **BGP ASN** , enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface. The valid values are 1 to 4294967294. This includes support for both ASNs (1-2147483647) and long ASNs (1-4294967294). For more information about ASNs and long ASNs see [Long ASN support in AWS Direct Connect](./long-asn-support.html). + 4. For **BGP ASN** , enter the The Border Gateway Protocol Autonomous System Number of your on-premises peer router for the new virtual interface. The valid values are 1 to 4294967294. This includes support for both ASNs (1-2147483647) and long ASNs (1-4294967294). For more information about ASNs and long ASNs see [Long ASN support in Direct Connect](./long-asn-support.html). @@ -307 +307 @@ If you do not enter a value, we generate a BGP key. - 1. Open the **AWS Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). + 1. Open the **Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). @@ -331 +331 @@ If you do not enter a value, we generate a BGP key. -The valid values are 1 to 4294967294. This includes support for both ASNs (1-2147483647) and long ASNs (1-4294967294). For more information about ASNs and long ASNs see [Long ASN support in AWS Direct Connect](./long-asn-support.html). +The valid values are 1 to 4294967294. This includes support for both ASNs (1-2147483647) and long ASNs (1-4294967294). For more information about ASNs and long ASNs see [Long ASN support in Direct Connect](./long-asn-support.html). @@ -376 +376 @@ When configuring AWS Direct Connect virtual interfaces, you can specify your own -After you have created a virtual interface for your AWS Direct Connect connection, you can download the router configuration file. The file contains the necessary commands to configure your router for use with your private or public virtual interface. +After you have created a virtual interface for your Direct Connect connection, you can download the router configuration file. The file contains the necessary commands to configure your router for use with your private or public virtual interface. @@ -380 +380 @@ After you have created a virtual interface for your AWS Direct Connect connectio - 1. Open the **AWS Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). + 1. Open the **Direct Connect** console at [https://console.aws.amazon.com/directconnect/v2/home](https://console.aws.amazon.com/directconnect/v2/home). @@ -396 +396 @@ After you have created a virtual interface for your AWS Direct Connect connectio - 6. Choose **Download** , and then use the appropriate configuration for your router to ensure that you can connect to AWS Direct Connect. + 6. Choose **Download** , and then use the appropriate configuration for your router to ensure that you can connect to Direct Connect. @@ -403 +403 @@ For more information about manually configuring your router, see [Download the r -After you configure your router, the status of the virtual interface goes to `UP`. If the virtual interface remains down and you cannot ping the AWS Direct Connect device's peer IP address, see [Troubleshoot layer 2 (data link) issues](./ts-layer-2.html). If you can ping the peer IP address, see [Troubleshoot layer 3/4 (Network/Transport) issues](./ts-layer-3.html). If the BGP peering session is established but you cannot route traffic, see [Troubleshoot routing issues](./ts-routing.html). +After you configure your router, the status of the virtual interface goes to `UP`. If the virtual interface remains down and you cannot ping the Direct Connect device's peer IP address, see [Troubleshoot layer 2 (data link) issues](./ts-layer-2.html). If you can ping the peer IP address, see [Troubleshoot layer 3/4 (Network/Transport) issues](./ts-layer-3.html). If the BGP peering session is established but you cannot route traffic, see [Troubleshoot routing issues](./ts-routing.html). @@ -411 +411 @@ After you have established virtual interfaces to the AWS Cloud or to Amazon VPC, - * Run `traceroute` and verify that the AWS Direct Connect identifier is in the network trace. + * Run `traceroute` and verify that the Direct Connect identifier is in the network trace. @@ -435 +435 @@ There are different configuration choices available when you provision two dedic - * Active/Active (BGP multipath). This is the default configuration, where both connections are active. AWS Direct Connect supports multipathing to multiple virtual interfaces within the same location, and traffic is load-shared between interfaces based on flow. If one connection becomes unavailable, all traffic is routed through the other connection. + * Active/Active (BGP multipath). This is the default configuration, where both connections are active. Direct Connect supports multipathing to multiple virtual interfaces within the same location, and traffic is load-shared between interfaces based on flow. If one connection becomes unavailable, all traffic is routed through the other connection. @@ -453 +453 @@ If you use a VPN connection for redundancy, ensure that you implement a health c -To achieve high availability, we strongly recommend that you configure connections to different AWS Direct Connect locations. +To achieve high availability, we strongly recommend that you configure connections to different Direct Connect locations. @@ -455 +455 @@ To achieve high availability, we strongly recommend that you configure connectio -For more information about AWS Direct Connect resiliency, see [AWS Direct Connect Resiliency Recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/). +For more information about Direct Connect resiliency, see [Direct Connect Resiliency Recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/).