AWS directconnect documentation change
Summary
Updated documentation to replace 'AWS Direct Connect' with 'Direct Connect' in multiple instances for branding consistency
Security assessment
The changes are purely branding/naming updates (removing 'AWS' prefix from service references). No security vulnerabilities, configuration changes, or security feature additions are mentioned. The modifications maintain existing security guidance about VLAN tags, BGP keys, and jumbo frames without altering their security implications.
Diff
diff --git a/directconnect/latest/UserGuide/max-resiliency-set-up.md b/directconnect/latest/UserGuide/max-resiliency-set-up.md index 49bca6ae2..a06c11353 100644 --- a//directconnect/latest/UserGuide/max-resiliency-set-up.md +++ b//directconnect/latest/UserGuide/max-resiliency-set-up.md @@ -9 +9 @@ Step 1: Sign up for AWSStep 2: Configure the resiliency modelStep 3: Create your -In this example, the AWS Direct Connect Resiliency Toolkit is used to configure a maximum resiliency model +In this example, the Direct Connect Resiliency Toolkit is used to configure a maximum resiliency model @@ -28 +28 @@ In this example, the AWS Direct Connect Resiliency Toolkit is used to configure -To use AWS Direct Connect, you need an AWS account if you don't already have one. +To use Direct Connect, you need an AWS account if you don't already have one. @@ -105 +105 @@ For instructions, see [ Add groups](https://docs.aws.amazon.com/singlesignon/lat - 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). @@ -119 +119 @@ This bandwidth applies to all of the created connections. - 2. For **First location service provider** , select the appropriate AWS Direct Connect location for the dedicated connection. + 2. For **First location service provider** , select the appropriate Direct Connect location for the dedicated connection. @@ -125 +125 @@ This bandwidth applies to all of the created connections. - 5. For **Second location service provider** , select the appropriate AWS Direct Connect location. + 5. For **Second location service provider** , select the appropriate Direct Connect location. @@ -160 +160 @@ 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. @@ -164 +164 @@ 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. @@ -190 +190 @@ 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: @@ -198 +198 @@ 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. @@ -206 +206 @@ 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). @@ -224 +224 @@ When you create a public virtual interface, it can take up to 72 business hours -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). @@ -261 +261 @@ 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). @@ -285 +285 @@ 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). @@ -328 +328 @@ When configuring AWS Direct Connect virtual interfaces, you can specify your own -After you have established virtual interfaces to the AWS Cloud or to Amazon VPC, perform a virtual interface failover test to verify that your configuration meets your resiliency requirements. For more information, see [AWS Direct Connect Failover Test](./resiliency_failover.html). +After you have established virtual interfaces to the AWS Cloud or to Amazon VPC, perform a virtual interface failover test to verify that your configuration meets your resiliency requirements. For more information, see [Direct Connect Failover Test](./resiliency_failover.html). @@ -336 +336 @@ 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.