AWS directconnect documentation change
Summary
Updated product name references from 'AWS Direct Connect' to 'Direct Connect' throughout the documentation. Changed section headers, descriptions, and links to use the simplified product name.
Security assessment
The changes are purely branding/nomenclature updates without any modifications to security configurations, protocols, or vulnerabilities. No security-related content was added or modified beyond grammatical updates. The BFD mention remains unchanged in substance.
Diff
diff --git a/directconnect/latest/UserGuide/Welcome.md b/directconnect/latest/UserGuide/Welcome.md index 4bea5f995..4c2d8fea9 100644 --- a//directconnect/latest/UserGuide/Welcome.md +++ b//directconnect/latest/UserGuide/Welcome.md @@ -7 +7 @@ Direct Connect componentsNetwork requirementsSupported Direct Connect virtual in -# What is AWS Direct Connect? +# What is Direct Connect? @@ -9 +9 @@ Direct Connect componentsNetwork requirementsSupported Direct Connect virtual in -AWS Direct Connect links your internal network to an AWS Direct Connect location over a standard Ethernet fiber-optic cable. One end of the cable is connected to your router, the other to an AWS Direct Connect router. With this connection, you can create _virtual interfaces_ directly to public AWS services (for example, to Amazon S3) or to Amazon VPC, bypassing internet service providers in your network path. An AWS Direct Connect location provides access to AWS in the Region with which it is associated. You can use a single connection in a public Region or AWS GovCloud (US) to access public AWS services in all other public Regions. +Direct Connect links your internal network to an Direct Connect location over a standard Ethernet fiber-optic cable. One end of the cable is connected to your router, the other to an Direct Connect router. With this connection, you can create _virtual interfaces_ directly to public AWS services (for example, to Amazon S3) or to Amazon VPC, bypassing internet service providers in your network path. An Direct Connect location provides access to AWS in the Region with which it is associated. You can use a single connection in a public Region or AWS GovCloud (US) to access public AWS services in all other public Regions. @@ -18 +18 @@ AWS Direct Connect links your internal network to an AWS Direct Connect location -The following diagram shows a high-level overview of how AWS Direct Connect interfaces with your network. +The following diagram shows a high-level overview of how Direct Connect interfaces with your network. @@ -20 +20 @@ The following diagram shows a high-level overview of how AWS Direct Connect inte - + @@ -39 +39 @@ The following diagram shows a high-level overview of how AWS Direct Connect inte -## AWS Direct Connect components +## Direct Connect components @@ -46 +46 @@ The following are the key components that you use for Direct Connect: -Create a _connection_ in an AWS Direct Connect location to establish a network connection from your premises to an AWS Region. For more information, see [AWS Direct Connect dedicated and hosted connections](./WorkingWithConnections.html). +Create a _connection_ in an Direct Connect location to establish a network connection from your premises to an AWS Region. For more information, see [Direct Connect dedicated and hosted connections](./WorkingWithConnections.html). @@ -51 +51 @@ Create a _connection_ in an AWS Direct Connect location to establish a network c -Create a _virtual interface_ to enable access to AWS services. A public virtual interface enables access to public services, such as Amazon S3. A private virtual interface enables access to your VPC. The types of supported interfaces are described below in Supported Direct Connect virtual interface types. For more details about the supported interfaces, see [AWS Direct Connect virtual interfaces and hosted virtual interfaces](./WorkingWithVirtualInterfaces.html) and [Prerequisites for virtual interfaces](./WorkingWithVirtualInterfaces.html#vif-prerequisites). +Create a _virtual interface_ to enable access to AWS services. A public virtual interface enables access to public services, such as Amazon S3. A private virtual interface enables access to your VPC. The types of supported interfaces are described below in Supported Direct Connect virtual interface types. For more details about the supported interfaces, see [Direct Connect virtual interfaces and hosted virtual interfaces](./WorkingWithVirtualInterfaces.html) and [Prerequisites for virtual interfaces](./WorkingWithVirtualInterfaces.html#vif-prerequisites). @@ -55 +55 @@ Create a _virtual interface_ to enable access to AWS services. A public virtual -To use AWS Direct Connect in an AWS Direct Connect location, your network must meet one of the following conditions: +To use Direct Connect in an Direct Connect location, your network must meet one of the following conditions: @@ -57 +57 @@ To use AWS Direct Connect in an AWS Direct Connect location, your network must m - * Your network is colocated with an existing AWS Direct Connect location. For more information about available AWS Direct Connect locations, see [AWS Direct Connect Product Details](https://aws.amazon.com/directconnect/details). + * Your network is colocated with an existing Direct Connect location. For more information about available Direct Connect locations, see [AWS Direct Connect Product Details](https://aws.amazon.com/directconnect/details). @@ -59 +59 @@ To use AWS Direct Connect in an AWS Direct Connect location, your network must m - * You are working with an AWS Direct Connect partner who is a member of the AWS Partner Network (APN). For information, see [APN Partners Supporting AWS Direct Connect](https://aws.amazon.com//directconnect/partners/). + * You are working with an Direct Connect partner who is a member of the AWS Partner Network (APN). For information, see [APN Partners Supporting AWS Direct Connect](https://aws.amazon.com//directconnect/partners/). @@ -61 +61 @@ To use AWS Direct Connect in an AWS Direct Connect location, your network must m - * You are working with an independent service provider to connect to AWS Direct Connect. + * You are working with an independent service provider to connect to Direct Connect. @@ -76 +76 @@ In addition, your network must meet the following conditions: - * (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/). + * (Optional) You can configure Bidirectional Forwarding Detection (BFD) on your network. Asynchronous BFD is automatically enabled for each 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/). @@ -81 +81 @@ In addition, your network must meet the following conditions: -AWS Direct Connect supports both the IPv4 and IPv6 communication protocols. IPv6 addresses provided by public AWS services are accessible through AWS Direct Connect public virtual interfaces. +Direct Connect supports both the IPv4 and IPv6 communication protocols. IPv6 addresses provided by public AWS services are accessible through Direct Connect public virtual interfaces. @@ -83 +83 @@ AWS Direct Connect supports both the IPv4 and IPv6 communication protocols. IPv6 -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. You can set the MTU of your private virtual interfaces. For more information, see [MTUs for private virtual interfaces or transit virtual interfaces](./WorkingWithVirtualInterfaces.html#set-jumbo-frames-vif). +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. You can set the MTU of your private virtual interfaces. For more information, see [MTUs for private virtual interfaces or transit virtual interfaces](./WorkingWithVirtualInterfaces.html#set-jumbo-frames-vif). @@ -112 +112 @@ There are limits to the number of different types of associations between a Dire -For more information about virtual interfaces, see [AWS Direct Connect virtual interfaces and hosted virtual interfaces](./WorkingWithVirtualInterfaces.html). +For more information about virtual interfaces, see [Direct Connect virtual interfaces and hosted virtual interfaces](./WorkingWithVirtualInterfaces.html). @@ -120 +120 @@ Data Transfer Out charges for private interfaces and transit virtual interfaces -For publicly addressable AWS resources (for example, Amazon S3 buckets, Classic EC2 instances, or EC2 traffic that goes through an internet gateway), if the outbound traffic is destined for public prefixes owned by the same AWS payer account and actively advertised to AWS through an AWS Direct Connect public virtual Interface, the Data Transfer Out (DTO) usage is metered toward the resource owner at AWS Direct Connect data transfer rate. +For publicly addressable AWS resources (for example, Amazon S3 buckets, Classic EC2 instances, or EC2 traffic that goes through an internet gateway), if the outbound traffic is destined for public prefixes owned by the same AWS payer account and actively advertised to AWS through an Direct Connect public virtual Interface, the Data Transfer Out (DTO) usage is metered toward the resource owner at Direct Connect data transfer rate.