AWS wellarchitected documentation change
Summary
Updated documentation links to use 'Site-to-Site VPN' terminology instead of 'AWS VPN' in two locations, maintaining the same URLs but aligning with product naming conventions.
Security assessment
The changes are purely terminological updates to align with product naming standards (e.g., 'AWS VPN' to 'Site-to-Site VPN'). There is no indication of addressing security vulnerabilities or adding new security-related content.
Diff
diff --git a/wellarchitected/latest/hybrid-networking-lens/reliability-pillar.md b/wellarchitected/latest/hybrid-networking-lens/reliability-pillar.md index d00a3e263..07d37804b 100644 --- a//wellarchitected/latest/hybrid-networking-lens/reliability-pillar.md +++ b//wellarchitected/latest/hybrid-networking-lens/reliability-pillar.md @@ -52 +52 @@ Being aware of how change affects a system enables you to plan proactively, and -Logs and metrics are a powerful tool to gain insight into the health of your workloads. Configure your workload to monitor CloudWatch logs and metrics to send notifications when thresholds are crossed or significant events occur. For example, with AWS Direct Connect, `ConnectionBpsIngress`, `ConnectionBpsEgress`, `ConnectionPpsEgress`, and `ConnectionPpsIngress` metrics help track the connection capacity utilization. For a comprehensive list of metrics, refer to the [AWS Direct Connect User Guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/monitoring-cloudwatch.html). For information about VPN metrics, refer to the [AWS VPN User Guide](https://docs.aws.amazon.com/vpn/latest/s2svpn/monitoring-cloudwatch-vpn.html). +Logs and metrics are a powerful tool to gain insight into the health of your workloads. Configure your workload to monitor CloudWatch logs and metrics to send notifications when thresholds are crossed or significant events occur. For example, with AWS Direct Connect, `ConnectionBpsIngress`, `ConnectionBpsEgress`, `ConnectionPpsEgress`, and `ConnectionPpsIngress` metrics help track the connection capacity utilization. For a comprehensive list of metrics, refer to the [AWS Direct Connect User Guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/monitoring-cloudwatch.html). For information about VPN metrics, refer to the [Site-to-Site VPN User Guide](https://docs.aws.amazon.com/vpn/latest/s2svpn/monitoring-cloudwatch-vpn.html). @@ -81 +81 @@ In any system of reasonable complexity, it’s expected that failures will occur -Highly resilient network connections are key to a well-architected system. AWS recommends connecting from multiple data centers for physical location redundancy. For more information, refer to [AWS Direct Connect resilency recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/). When designing remote connections, consider using redundant hardware and telecommunications providers. Your telecommunication provider should have a diverse fiber and path connectivity for your last mile connection or offer any SLA. Ensure that the physical infrastructure configuration you set up is in accordance with the requirements to meet [AWS Direct Connect SLA](https://aws.amazon.com/directconnect/sla/) and [AWS VPN SLA](https://aws.amazon.com/vpn/site-to-site-vpn-sla/). Additionally, use dynamically routed, Active/Active connections for automatic load balancing and failover across redundant network connections. Provision sufficient network capacity to ensure that the failure of one network connection does not overwhelm and degrade redundant connections. +Highly resilient network connections are key to a well-architected system. AWS recommends connecting from multiple data centers for physical location redundancy. For more information, refer to [AWS Direct Connect resilency recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/). When designing remote connections, consider using redundant hardware and telecommunications providers. Your telecommunication provider should have a diverse fiber and path connectivity for your last mile connection or offer any SLA. Ensure that the physical infrastructure configuration you set up is in accordance with the requirements to meet [AWS Direct Connect SLA](https://aws.amazon.com/directconnect/sla/) and [Site-to-Site VPN SLA](https://aws.amazon.com/vpn/site-to-site-vpn-sla/). Additionally, use dynamically routed, Active/Active connections for automatic load balancing and failover across redundant network connections. Provision sufficient network capacity to ensure that the failure of one network connection does not overwhelm and degrade redundant connections.