AWS wellarchitected documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' and adjusted toolkit naming for consistency
Security assessment
Changes focus on branding consistency (removing redundant 'AWS' prefix) and toolkit name updates. No security-related content modifications or additions.
Diff
diff --git a/wellarchitected/latest/reliability-pillar/rel_planning_network_topology_ha_conn_private_networks.md b/wellarchitected/latest/reliability-pillar/rel_planning_network_topology_ha_conn_private_networks.md index 9c65fe1c1..360535b8d 100644 --- a//wellarchitected/latest/reliability-pillar/rel_planning_network_topology_ha_conn_private_networks.md +++ b//wellarchitected/latest/reliability-pillar/rel_planning_network_topology_ha_conn_private_networks.md @@ -32 +32 @@ Implement redundancy in your connections between private networks in the cloud a -When using AWS Direct Connect to connect your on-premises network to AWS, you can achieve maximum network resiliency (SLA of 99.99%) by using separate connections that end on distinct devices in more than one on-premises location and more than one AWS Direct Connect location. This topology offers resilience against device failures, connectivity issues, and complete location outages. Alternatively, you can achieve high resiliency (SLA of 99.9%) by using two individual connections to multiple locations (each on-premises location connected to a single Direct Connect location). This approach protects against connectivity disruptions caused by fiber cuts or device failures and helps mitigate complete location failures. The AWS Direct Connect Resiliency Toolkit can assist in designing your AWS Direct Connect topology. +When using AWS Direct Connect to connect your on-premises network to AWS, you can achieve maximum network resiliency (SLA of 99.99%) by using separate connections that end on distinct devices in more than one on-premises location and more than one AWS Direct Connect location. This topology offers resilience against device failures, connectivity issues, and complete location outages. Alternatively, you can achieve high resiliency (SLA of 99.9%) by using two individual connections to multiple locations (each on-premises location connected to a single Direct Connect location). This approach protects against connectivity disruptions caused by fiber cuts or device failures and helps mitigate complete location failures. The Direct Connect Resiliency Toolkit can assist in designing your AWS Direct Connect topology. @@ -46 +46 @@ In addition to physical redundancy with multiple AWS Direct Connect connections - * Use multiple AWS Direct Connect locations for high availability. + * Use multiple Direct Connect locations for high availability. @@ -58 +58 @@ In addition to physical redundancy with multiple AWS Direct Connect connections - * Use the [AWS Direct Connect Resiliency Toolkit](https://docs.aws.amazon.com/directconnect/latest/UserGuide/resilency_toolkit.html) to get started. + * Use the [Direct Connect Resiliency Toolkit](https://docs.aws.amazon.com/directconnect/latest/UserGuide/resilency_toolkit.html) to get started. @@ -85 +85 @@ In addition to physical redundancy with multiple AWS Direct Connect connections - * [Using the AWS Direct Connect Resiliency Toolkit to get started](https://docs.aws.amazon.com/directconnect/latest/UserGuide/resilency_toolkit.html) + * [Using the Direct Connect Resiliency Toolkit to get started](https://docs.aws.amazon.com/directconnect/latest/UserGuide/resilency_toolkit.html)