AWS architecture-diagrams documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' throughout the document for consistency
Security assessment
Changes are purely branding/terminology updates (removing redundant 'AWS' prefix from 'Direct Connect' references). No security vulnerabilities, mitigations, or security feature enhancements are mentioned or implied in the changes.
Diff
diff --git a/architecture-diagrams/latest/active-active-and-active-passive-configurations-in-aws-direct-connect/active-active-and-active-passive-configurations-in-aws-direct-connect.md b/architecture-diagrams/latest/active-active-and-active-passive-configurations-in-aws-direct-connect/active-active-and-active-passive-configurations-in-aws-direct-connect.md index 4f3147e75..0cd99f2a5 100644 --- a//architecture-diagrams/latest/active-active-and-active-passive-configurations-in-aws-direct-connect/active-active-and-active-passive-configurations-in-aws-direct-connect.md +++ b//architecture-diagrams/latest/active-active-and-active-passive-configurations-in-aws-direct-connect/active-active-and-active-passive-configurations-in-aws-direct-connect.md @@ -15 +15 @@ Amazon Web Services offers customers the ability to achieve highly-resilient net -This reference architecture focuses on the Maximum Resiliency model, which provides you with a way to order dedicated connections to achieve an SLA of 99.99%. You can find the requirements in the [AWS Direct Connect Service Level Agreement](https://aws.amazon.com/directconnect/sla/). +This reference architecture focuses on the Maximum Resiliency model, which provides you with a way to order dedicated connections to achieve an SLA of 99.99%. You can find the requirements in the [Direct Connect Service Level Agreement](https://aws.amazon.com/directconnect/sla/). @@ -19 +19 @@ This reference architecture focuses on the Maximum Resiliency model, which provi -For Active/Active mode, you can leverage [LAGs](https://docs.aws.amazon.com/directconnect/latest/UserGuide/lags.html) for dedicated AWS Direct Connect connections, terminating on the same AWS Direct Connect endpoint. This will load balance traffic across all connections in the LAG on layer 2. This will not protect against failure on the AWS Direct Connect endpoint or the whole AWS Direct Connect location. +For Active/Active mode, you can leverage [LAGs](https://docs.aws.amazon.com/directconnect/latest/UserGuide/lags.html) for dedicated Direct Connect connections, terminating on the same Direct Connect endpoint. This will load balance traffic across all connections in the LAG on layer 2. This will not protect against failure on the Direct Connect endpoint or the whole Direct Connect location. @@ -21 +21 @@ For Active/Active mode, you can leverage [LAGs](https://docs.aws.amazon.com/dire -With ECMP, you can load balance traffic across multiple connections and AWS Direct Connect locations on layer 3. You can influence path behaviour by longest prefix match and Border Gateway Protocol (BGP) attributes. This allows for setting up Active/Active or Active/Passive configurations. +With ECMP, you can load balance traffic across multiple connections and Direct Connect locations on layer 3. You can influence path behaviour by longest prefix match and Border Gateway Protocol (BGP) attributes. This allows for setting up Active/Active or Active/Passive configurations. @@ -25 +25 @@ With ECMP, you can load balance traffic across multiple connections and AWS Dire -Build Active/Active configuration with Transit/Private Virtual Interface (VIF) for max resiliency. Have redundant AWS Direct Connect connections inside each AWS Direct Connect location as well as across locations, customer data centers, and devices. This configuration offers customers max resilience to failure. Such a topology ensures resilience to connectivity failure due to a fiber cut or a device failure as well as a complete location failure. +Build Active/Active configuration with Transit/Private Virtual Interface (VIF) for max resiliency. Have redundant Direct Connect connections inside each Direct Connect location as well as across locations, customer data centers, and devices. This configuration offers customers max resilience to failure. Such a topology ensures resilience to connectivity failure due to a fiber cut or a device failure as well as a complete location failure. @@ -38 +38 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 2. When you request multiple ports at the same **AWS Direct Connect** location, they will be provisioned on redundant AWS equipment. + 2. When you request multiple ports at the same **Direct Connect** location, they will be provisioned on redundant AWS equipment. @@ -40 +40 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 3. **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. + 3. **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. @@ -42 +42 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 4. Have the redundant **AWS Direct Connect** connections terminate on different customer/partner routers inside the **AWS Direct Connect** location. + 4. Have the redundant **Direct Connect** connections terminate on different customer/partner routers inside the **Direct Connect** location. @@ -44 +44 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 5. **AWS Direct Connect** connections have to be brought down for regular scheduled maintenance. Therefore, use multiple connections. + 5. **Direct Connect** connections have to be brought down for regular scheduled maintenance. Therefore, use multiple connections. @@ -46 +46 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 6. Have the redundant **AWS Direct Connect** connections terminate on different routers inside your data center. + 6. Have the redundant **Direct Connect** connections terminate on different routers inside your data center. @@ -48 +48 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 7. Use multiple **AWS Direct Connect** connections across multiple **AWS Direct Connect** locations. + 7. Use multiple **Direct Connect** connections across multiple **Direct Connect** locations. @@ -50 +50 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 8. Use multiple **AWS Direct Connect** connections across multiple customer sites. + 8. Use multiple **Direct Connect** connections across multiple customer sites. @@ -52 +52 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 9. Advertise the same prefixes across all **AWS Direct Connect** connections for Active/Active setup. + 9. Advertise the same prefixes across all **Direct Connect** connections for Active/Active setup. @@ -54 +54 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 10. If prefixes are the same, a higher local preference is preferred. By using BGP communities you can set the local preference from 7224:7100/7200/7300 where 7100 is low, 7200 is medium, and 7300 is high preference. Use the same local preference across all **AWS Direct Connect** connections for an Active/Active setup. + 10. If prefixes are the same, a higher local preference is preferred. By using BGP communities you can set the local preference from 7224:7100/7200/7300 where 7100 is low, 7200 is medium, and 7300 is high preference. Use the same local preference across all **Direct Connect** connections for an Active/Active setup. @@ -56 +56 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 11. If local preference is the same, shortest AS paths are preferred across **AWS Direct Connect** connections associated with the same AWS Region. Use the same AS path length across all **AWS Direct Connect** connections for an Active/Active setup. + 11. If local preference is the same, shortest AS paths are preferred across **Direct Connect** connections associated with the same AWS Region. Use the same AS path length across all **Direct Connect** connections for an Active/Active setup. @@ -58 +58 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 12. If AS path lengths are the same, a lower MED value will be preferred. For an Active/Active setup, use the same MED value for all **AWS Direct Connect** connections. + 12. If AS path lengths are the same, a lower MED value will be preferred. For an Active/Active setup, use the same MED value for all **Direct Connect** connections. @@ -60 +60 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f - 13. You can create LAGs for dedicated connections terminating at the same **AWS Direct Connect** endpoint. All connections in a LAG operate in Active/Active mode. + 13. You can create LAGs for dedicated connections terminating at the same **Direct Connect** endpoint. All connections in a LAG operate in Active/Active mode. @@ -67 +67 @@ Build Active/Active configuration with Transit/Private Virtual Interface (VIF) f -Build Active/Passive configuration with Transit/Private VIF for max resiliency. Have redundant AWS Direct Connect connections inside each AWS Direct Connect location as well as across locations, customer data centers and devices. This configuration offers customers max resilience to failure. Such a topology ensures resilience to connectivity failure due to a fiber cut or a device failure as well as a complete location failure. +Build Active/Passive configuration with Transit/Private VIF for max resiliency. Have redundant Direct Connect connections inside each Direct Connect location as well as across locations, customer data centers and devices. This configuration offers customers max resilience to failure. Such a topology ensures resilience to connectivity failure due to a fiber cut or a device failure as well as a complete location failure. @@ -78 +78 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 1. **AWS Direct Connect** gateway is a global construct and AWS takes care of its availability. + 1. **Direct Connect** gateway is a global construct and AWS takes care of its availability. @@ -80 +80 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 2. When you request multiple ports at the same **AWS Direct Connect** location, they will be provisioned on redundant AWS equipment. + 2. When you request multiple ports at the same **Direct Connect** location, they will be provisioned on redundant AWS equipment. @@ -82 +82 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 3. Have the redundant **AWS Direct Connect** connections terminate on different customer/partner routers inside the **AWS Direct Connect** location. + 3. Have the redundant **Direct Connect** connections terminate on different customer/partner routers inside the **Direct Connect** location. @@ -84 +84 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 4. **AWS Direct Connect** connections have to be brought down for regular scheduled maintenance. Therefore, use multiple connections. + 4. **Direct Connect** connections have to be brought down for regular scheduled maintenance. Therefore, use multiple connections. @@ -86 +86 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 5. Have the redundant **AWS Direct Connect** connections terminate on different routers inside your data center. + 5. Have the redundant **Direct Connect** connections terminate on different routers inside your data center. @@ -88 +88 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 6. Leverage multiple **AWS Direct Connect** connections across multiple **AWS Direct Connect** locations. + 6. Leverage multiple **Direct Connect** connections across multiple **Direct Connect** locations. @@ -90 +90 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 7. Leverage multiple **AWS Direct Connect** connections across multiple customer sites. + 7. Leverage multiple **Direct Connect** connections across multiple customer sites. @@ -92 +92 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 8. By advertising more specific prefixes you can prefer one **AWS Direct Connect** connection over the others. + 8. By advertising more specific prefixes you can prefer one **Direct Connect** connection over the others. @@ -94 +94 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 9. If prefixes are the same, a higher local preference is preferred. By using BGP communities you can set a local preference from 7224:7100/7200/7300 where 7100 is low, 7200 is medium, and 7300 is high preference. Use a higher local preference to prefer a specific **AWS Direct Connect** connection over others. + 9. If prefixes are the same, a higher local preference is preferred. By using BGP communities you can set a local preference from 7224:7100/7200/7300 where 7100 is low, 7200 is medium, and 7300 is high preference. Use a higher local preference to prefer a specific **Direct Connect** connection over others. @@ -96 +96 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 10. If local preference is the same, shortest AS paths are preferred. You can use AS path prepending for **AWS Direct Connect** connections associated with the same AWS Region. AWS will prefer the shorter AS path for multiple virtual interfaces in a Region. + 10. If local preference is the same, shortest AS paths are preferred. You can use AS path prepending for **Direct Connect** connections associated with the same AWS Region. AWS will prefer the shorter AS path for multiple virtual interfaces in a Region. @@ -98 +98 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. - 11. Use a lower MED value to prefer a specific **AWS Direct Connect** connection. + 11. Use a lower MED value to prefer a specific **Direct Connect** connection. @@ -105 +105 @@ Build Active/Passive configuration with Transit/Private VIF for max resiliency. -Build Active/Active configuration with Public VIF for max resiliency. Have redundant AWS Direct Connect connections inside each AWS Direct Connect location as well as across locations, customer data centers, and devices. This configuration offers customers max resilience to failure. Such a topology ensures resilience to connectivity failure due to a fiber cut or a device failure as well as a complete location failure. +Build Active/Active configuration with Public VIF for max resiliency. Have redundant Direct Connect connections inside each Direct Connect location as well as across locations, customer data centers, and devices. This configuration offers customers max resilience to failure. Such a topology ensures resilience to connectivity failure due to a fiber cut or a device failure as well as a complete location failure. @@ -118 +118 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 1. When you request multiple ports at the same **AWS Direct Connect** location, they will be provisioned on redundant AWS equipment. + 1. When you request multiple ports at the same **Direct Connect** location, they will be provisioned on redundant AWS equipment. @@ -120 +120 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 2. **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. + 2. **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. @@ -122 +122 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 3. Have the redundant **AWS Direct Connect** connections terminate on different customer/partner routers inside the **AWS Direct Connect** location. + 3. Have the redundant **Direct Connect** connections terminate on different customer/partner routers inside the **Direct Connect** location. @@ -124 +124 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 4. **AWS Direct Connect** connections have to be brought down for regular scheduled maintenance. Therefore, use multiple connections. + 4. **Direct Connect** connections have to be brought down for regular scheduled maintenance. Therefore, use multiple connections. @@ -126 +126 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 5. Have the redundant **AWS Direct Connect** connections terminate on different routers inside your data center. + 5. Have the redundant **Direct Connect** connections terminate on different routers inside your data center. @@ -128 +128 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 6. Leverage multiple **AWS Direct Connect** connections across multiple **AWS Direct Connect** locations. + 6. Leverage multiple **Direct Connect** connections across multiple **Direct Connect** locations. @@ -130 +130 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 7. Leverage multiple **AWS Direct Connect** connections across multiple customer sites. + 7. Leverage multiple **Direct Connect** connections across multiple customer sites. @@ -132 +132 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 8. Advertise the same prefixes across all **AWS Direct Connect** connections for Active/Active setup. + 8. Advertise the same prefixes across all **Direct Connect** connections for Active/Active setup. @@ -134 +134 @@ If you're using a private ASN, load balancing on a public virtual interface is n - 9. If prefixes are the same, shortest AS paths are preferred. Use the same AS path length across all **AWS Direct Connect** connections for an Active/Active setup. + 9. If prefixes are the same, shortest AS paths are preferred. Use the same AS path length across all **Direct Connect** connections for an Active/Active setup. @@ -141 +141 @@ If you're using a private ASN, load balancing on a public virtual interface is n -Build Active/Passive configuration with Public VIF for max resiliency. Have redundant AWS Direct Connect connections inside each AWS Direct Connect location as well as across locations, customer data centers and devices. This configuration offers customers max resilience to failure. Such a topology ensures resilience to connectivity failure due to a fiber cut or a device failure as well as a complete location failure. +Build Active/Passive configuration with Public VIF for max resiliency. Have redundant Direct Connect connections inside each Direct Connect location as well as across locations, customer data centers and devices. This configuration offers customers max resilience to failure. Such a topology ensures resilience to connectivity failure due to a fiber cut or a device failure as well as a complete location failure. @@ -152 +152 @@ Build Active/Passive configuration with Public VIF for max resiliency. Have redu - 1. When you request multiple ports at the same **AWS Direct Connect** location, they will be provisioned on redundant AWS equipment. + 1. When you request multiple ports at the same **Direct Connect** location, they will be provisioned on redundant AWS equipment. @@ -154 +154 @@ Build Active/Passive configuration with Public VIF for max resiliency. Have redu - 2. Have the redundant **AWS Direct Connect** connections terminate on different customer/partner routers inside the **AWS Direct Connect** location. + 2. Have the redundant **Direct Connect** connections terminate on different customer/partner routers inside the **Direct Connect** location. @@ -156 +156 @@ Build Active/Passive configuration with Public VIF for max resiliency. Have redu - 3. **AWS Direct Connect** connections have to be brought down for regular scheduled maintenance. Therefore, use multiple connections. + 3. **Direct Connect** connections have to be brought down for regular scheduled maintenance. Therefore, use multiple connections. @@ -158 +158 @@ Build Active/Passive configuration with Public VIF for max resiliency. Have redu - 4. Have the redundant **AWS Direct Connect** connections terminate on different routers inside your data center. + 4. Have the redundant **Direct Connect** connections terminate on different routers inside your data center. @@ -160 +160 @@ Build Active/Passive configuration with Public VIF for max resiliency. Have redu - 5. Leverage multiple **AWS Direct Connect** connections across multiple **AWS Direct Connect** locations. + 5. Leverage multiple **Direct Connect** connections across multiple **Direct Connect** locations. @@ -162 +162 @@ Build Active/Passive configuration with Public VIF for max resiliency. Have redu - 6. Leverage multiple **AWS Direct Connect** connections across multiple customer sites. + 6. Leverage multiple **Direct Connect** connections across multiple customer sites. @@ -164 +164 @@ Build Active/Passive configuration with Public VIF for max resiliency. Have redu - 7. By advertising more specific prefixes, you can prefer one **AWS Direct Connect** connection over the others. + 7. By advertising more specific prefixes, you can prefer one **Direct Connect** connection over the others. @@ -166 +166 @@ Build Active/Passive configuration with Public VIF for max resiliency. Have redu - 8. For public ASNs, if prefixes are the same, shortest AS paths are preferred. Use shorter AS path length to prefer a specific **AWS Direct Connect** connection over the others. + 8. For public ASNs, if prefixes are the same, shortest AS paths are preferred. Use shorter AS path length to prefer a specific **Direct Connect** connection over the others.