AWS architecture-diagrams documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in multiple sections and links to match branding consistency
Security assessment
Changes involve branding/naming convention updates (removing redundant 'AWS' prefix from 'Direct Connect' references). No security vulnerabilities, mitigations, or security features are mentioned or modified in the content. The updates are purely terminological without altering technical security implications of the described architectures.
Diff
diff --git a/architecture-diagrams/latest/traffic-segmentation-aws-direct-connect/traffic-segmentation-aws-direct-connect.md b/architecture-diagrams/latest/traffic-segmentation-aws-direct-connect/traffic-segmentation-aws-direct-connect.md index 0f6eca208..8627266fe 100644 --- a//architecture-diagrams/latest/traffic-segmentation-aws-direct-connect/traffic-segmentation-aws-direct-connect.md +++ b//architecture-diagrams/latest/traffic-segmentation-aws-direct-connect/traffic-segmentation-aws-direct-connect.md @@ -5 +5 @@ -Segment Your Traffic over AWS Direct Connect by Using Several Private VIFs in the VPC or AWS Direct Connect Gateway DiagramSegment Your Traffic over AWS Direct Connect by Using Several Transit VIFs and AWS Direct Connect Gateways DiagramUse AWS Transit Gateway Connect Attachments and AWS Direct Connect to Extend your On-Premises VRFs over Transit VIFs DiagramUse AWS Site-to-Site VPN Attachments (Public VIFs) and AWS Direct Connect to Extend Your On-Premises VRFs DiagramUse AWS Site-to-Site VPN Private IP VPN Attachments and AWS Direct Connect to Extend Your On-Premises VRFs Over Transit VIFs DiagramDownload editable diagramCreate a free AWS accountFurther readingContributorsDiagram history +Segment Your Traffic over AWS Direct Connect by Using Several Private VIFs in the VPC or Direct Connect Gateway DiagramSegment Your Traffic over AWS Direct Connect by Using Several Transit VIFs and Direct Connect Gateways DiagramUse AWS Transit Gateway Connect Attachments and AWS Direct Connect to Extend your On-Premises VRFs over Transit VIFs DiagramUse AWS Site-to-Site VPN Attachments (Public VIFs) and AWS Direct Connect to Extend Your On-Premises VRFs DiagramUse AWS Site-to-Site VPN Private IP VPN Attachments and AWS Direct Connect to Extend Your On-Premises VRFs Over Transit VIFs DiagramDownload editable diagramCreate a free AWS accountFurther readingContributorsDiagram history @@ -11 +11 @@ Publication date: **November 9, 2023 (Diagram history)** -This architecture shows traffic segmentation options in AWS Direct Connect, include using several private VIFs in the VPC or AWS Direct Connect gateway, using AWS Transit Gateway Connect attachments over transit VIF, and using AWS Site-to-Site VPN connections over transit VIF. +This architecture shows traffic segmentation options in AWS Direct Connect, include using several private VIFs in the VPC or Direct Connect gateway, using AWS Transit Gateway Connect attachments over transit VIF, and using AWS Site-to-Site VPN connections over transit VIF. @@ -13 +13 @@ This architecture shows traffic segmentation options in AWS Direct Connect, incl -## Segment Your Traffic over AWS Direct Connect by Using Several Private VIFs in the VPC or AWS Direct Connect Gateway Diagram +## Segment Your Traffic over AWS Direct Connect by Using Several Private VIFs in the VPC or Direct Connect Gateway Diagram @@ -15 +15 @@ This architecture shows traffic segmentation options in AWS Direct Connect, incl - + @@ -17 +17 @@ This architecture shows traffic segmentation options in AWS Direct Connect, incl -Private virtual interfaces (VIFs) are used to access Amazon Virtual Private Cloud (Amazon VPC) using private IP addresses. Each VIF is configured with an unique virtual local area network (VLAN) tag, which means you can segment your traffic by using one VIF per virtual routing and forwarding (VRF) you have in your data center. Take into account the limits in the number of VIFs, depending the type of AWS Direct Connect connection you have. You can have 50 private or public VIFs with a dedicated connection, and one private or public VIF with a hosted connection. In addition, you can have 30 private VIFs associated to the same AWS Direct Connect gateway. You can check the quotas in the [AWS Direct Connect user guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html). +Private virtual interfaces (VIFs) are used to access Amazon Virtual Private Cloud (Amazon VPC) using private IP addresses. Each VIF is configured with an unique virtual local area network (VLAN) tag, which means you can segment your traffic by using one VIF per virtual routing and forwarding (VRF) you have in your data center. Take into account the limits in the number of VIFs, depending the type of Direct Connect connection you have. You can have 50 private or public VIFs with a dedicated connection, and one private or public VIF with a hosted connection. In addition, you can have 30 private VIFs associated to the same Direct Connect gateway. You can check the quotas in the [Direct Connect user guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html). @@ -21 +21 @@ Private virtual interfaces (VIFs) are used to access Amazon Virtual Private Clou - 2. The virtual private gateway is associated with the **AWS Direct Connect** gateway, which uses a private VIF (VLAN) to connect to the corporate data center. To achieve segmentation, use several private VIFs. The on-premises router must be configured to use a different VIF (VLAN) connection per VRF configured. + 2. The virtual private gateway is associated with the **Direct Connect** gateway, which uses a private VIF (VLAN) to connect to the corporate data center. To achieve segmentation, use several private VIFs. The on-premises router must be configured to use a different VIF (VLAN) connection per VRF configured. @@ -27 +27 @@ Private virtual interfaces (VIFs) are used to access Amazon Virtual Private Clou - 5. The customer gateway uses private VIF B – over the AWS Direct Connect link – to send the traffic to the virtual private gateway in VPC B. + 5. The customer gateway uses private VIF B – over the Direct Connect link – to send the traffic to the virtual private gateway in VPC B. @@ -34 +34 @@ Private virtual interfaces (VIFs) are used to access Amazon Virtual Private Clou -## Segment Your Traffic over AWS Direct Connect by Using Several Transit VIFs and AWS Direct Connect Gateways Diagram +## Segment Your Traffic over AWS Direct Connect by Using Several Transit VIFs and Direct Connect Gateways Diagram @@ -36 +36 @@ Private virtual interfaces (VIFs) are used to access Amazon Virtual Private Clou - + @@ -38 +38 @@ Private virtual interfaces (VIFs) are used to access Amazon Virtual Private Clou -Transit Virtual Interfaces (VIFs) are used to access AWS Transit Gateway by way of an AWS Direct Connect gateway. Each VIF is configured with an unique virtual local area network (VLAN) tag, which means you can segment your traffic by using one VIF per virtual routing and forwarding (VRF) you have in your data center. Take into account the limits in the number of VIFs, depending the type of AWS Direct Connect connection you have. You can have four transit VIFs with a max combination of 51 private, public, and transit VIFs per dedicated connection. For hosted connections, you can have only one transit VIF. In addition, you can have 30 transit VIFs associated with the same AWS Direct Connect gateway. You can check the quotas in the [AWS Direct Connect user guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html). +Transit Virtual Interfaces (VIFs) are used to access AWS Transit Gateway by way of an Direct Connect gateway. Each VIF is configured with an unique virtual local area network (VLAN) tag, which means you can segment your traffic by using one VIF per virtual routing and forwarding (VRF) you have in your data center. Take into account the limits in the number of VIFs, depending the type of Direct Connect connection you have. You can have four transit VIFs with a max combination of 51 private, public, and transit VIFs per dedicated connection. For hosted connections, you can have only one transit VIF. In addition, you can have 30 transit VIFs associated with the same Direct Connect gateway. You can check the quotas in the [Direct Connect user guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html). @@ -42 +42 @@ Transit Virtual Interfaces (VIFs) are used to access AWS Transit Gateway by way - 2. Transit Gateway is associated with several AWS Direct Connect gateways (DXGW), each one of them using a transit VIF (VLAN) to connect to the corporate data center, achieving traffic segmentation. The on-premises router must be configured to use a different VIF (VLAN) connection per VRF configured. + 2. Transit Gateway is associated with several Direct Connect gateways (DXGW), each one of them using a transit VIF (VLAN) to connect to the corporate data center, achieving traffic segmentation. The on-premises router must be configured to use a different VIF (VLAN) connection per VRF configured. @@ -50 +50 @@ Transit Virtual Interfaces (VIFs) are used to access AWS Transit Gateway by way - 6. The customer gateway uses transit VIF B – over the **AWS Direct Connect** link – to send the traffic to **Transit Gateway** Segment B. + 6. The customer gateway uses transit VIF B – over the **Direct Connect** link – to send the traffic to **Transit Gateway** Segment B. @@ -69 +69 @@ With a hosted connection, you get one transit VIF; with a dedicated connection y - 3. The **Transit Gateway** Connect attachment uses the **AWS Direct Connect** connection as transport and connects **Transit Gateway** to the corporate data center router using Generic Routing Encapsulation (GRE) tunneling and Border Gateway Protocol (BGP). The on-premises router must be configured to use a different connect attachment per VRF configured. + 3. The **Transit Gateway** Connect attachment uses the **Direct Connect** connection as transport and connects **Transit Gateway** to the corporate data center router using Generic Routing Encapsulation (GRE) tunneling and Border Gateway Protocol (BGP). The on-premises router must be configured to use a different connect attachment per VRF configured. @@ -75 +75 @@ With a hosted connection, you get one transit VIF; with a dedicated connection y - 6. The customer gateway uses the GRE tunnel of the **Transit Gateway** Connect attachment B – over the **AWS Direct Connect** link – to send the traffic to **Transit Gateway**. + 6. The customer gateway uses the GRE tunnel of the **Transit Gateway** Connect attachment B – over the **Direct Connect** link – to send the traffic to **Transit Gateway**. @@ -100 +100 @@ If your customer gateway does not support Generic Routing Encapsulation (GRE), y - 6. The customer gateway chooses **Site-to-Site VPN** connection B to send the traffic to the **Transit Gateway** over the **AWS Direct Connect** link. + 6. The customer gateway chooses **Site-to-Site VPN** connection B to send the traffic to the **Transit Gateway** over the **Direct Connect** link. @@ -119 +119 @@ If your customer gateway does not support GRE (Generic Routing Encapsulation), y - 3. The **Transit Gateway** **Site-to-Site VPN** attachment uses the **AWS Direct Connect** connection as transport, and connects **Transit Gateway** to the corporate data center router using one IPSec VPN connection (with two tunnels). The on-premises router must be configured to use a different VPN attachment per VRF configured. + 3. The **Transit Gateway** **Site-to-Site VPN** attachment uses the **Direct Connect** connection as transport, and connects **Transit Gateway** to the corporate data center router using one IPSec VPN connection (with two tunnels). The on-premises router must be configured to use a different VPN attachment per VRF configured. @@ -125 +125 @@ If your customer gateway does not support GRE (Generic Routing Encapsulation), y - 6. The customer gateway uses **Site-to-Site VPN** connection B – over the **AWS Direct Connect** link – to send the traffic to **Transit Gateway**. + 6. The customer gateway uses **Site-to-Site VPN** connection B – over the **Direct Connect** link – to send the traffic to **Transit Gateway**. @@ -154 +154 @@ For additional information, refer to - * [AWS Direct Connect user guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html) + * [Direct Connect user guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html) @@ -176 +176 @@ Change| Description| Date -Diagram updated| Added _Segment Your Traffic over AWS Direct Connect by Using Several Transit VIFs and AWS Direct Connect Gateways_ | November 9, 2023 +Diagram updated| Added _Segment Your Traffic over AWS Direct Connect by Using Several Transit VIFs and Direct Connect Gateways_ | November 9, 2023