AWS prescriptive-guidance documentation change
Summary
Changed references from 'AWS Direct Connect' to 'Direct Connect' throughout the document to align with service naming conventions
Security assessment
This change is purely stylistic/naming convention update regarding service references. No security-related content was added or modified - existing security references to 'secure, high-speed links' and VPN appliance recommendations remain unchanged. The modifications maintain equivalent security posture guidance.
Diff
diff --git a/prescriptive-guidance/latest/hybrid-cloud-best-practices/resiliency.md b/prescriptive-guidance/latest/hybrid-cloud-best-practices/resiliency.md index 644447535..64ad2ecfc 100644 --- a//prescriptive-guidance/latest/hybrid-cloud-best-practices/resiliency.md +++ b//prescriptive-guidance/latest/hybrid-cloud-best-practices/resiliency.md @@ -66 +66 @@ This section discusses initial considerations for networking at the edge, mainly -Local Zones are connected to the parent Region with multiple, redundant, secure, high-speed links that enable you to consume any Regional service, such as Amazon S3 and Amazon RDS, seamlessly. You are responsible for providing connectivity from your on-premises environment or users to the Local Zone. Regardless of the connectivity architecture you choose (for example, VPN or AWS Direct Connect), the latency that must be achieved through the network links must be equivalent to avoid any impact on application performance in the event of a failure in a main link. If you're using AWS Direct Connect, the applicable resilience architectures are the same as those for accessing an AWS Region, as documented in [AWS Direct Connect resiliency recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/). However, there are scenarios that apply mostly to international Local Zones. In the country where the Local Zone is enabled, having only a single AWS Direct Connect PoP makes it impossible to create the architectures recommended for AWS Direct Connect resilience. If you have access to only a single AWS Direct Connect location or require resiliency beyond a single connection, you can create a VPN appliance on Amazon EC2 and AWS Direct Connect, as illustrated and discussed in the AWS blog post [Enabling highly available connectivity from on premises to AWS Local Zones](https://aws.amazon.com/blogs/compute/enabling-highly-available-connectivity-from-on-premises-to-aws-local-zones/). +Local Zones are connected to the parent Region with multiple, redundant, secure, high-speed links that enable you to consume any Regional service, such as Amazon S3 and Amazon RDS, seamlessly. You are responsible for providing connectivity from your on-premises environment or users to the Local Zone. Regardless of the connectivity architecture you choose (for example, VPN or Direct Connect), the latency that must be achieved through the network links must be equivalent to avoid any impact on application performance in the event of a failure in a main link. If you're using Direct Connect, the applicable resilience architectures are the same as those for accessing an AWS Region, as documented in [Direct Connect resiliency recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/). However, there are scenarios that apply mostly to international Local Zones. In the country where the Local Zone is enabled, having only a single Direct Connect PoP makes it impossible to create the architectures recommended for Direct Connect resilience. If you have access to only a single Direct Connect location or require resiliency beyond a single connection, you can create a VPN appliance on Amazon EC2 and Direct Connect, as illustrated and discussed in the AWS blog post [Enabling highly available connectivity from on premises to AWS Local Zones](https://aws.amazon.com/blogs/compute/enabling-highly-available-connectivity-from-on-premises-to-aws-local-zones/). @@ -82 +82 @@ For more information about this connectivity, see [Local network connectivity fo -For an optimal experience and resiliency, AWSrecommends that you use redundant connectivity of at least 500 Mbps (1 Gbps is better) for the service link connection to the AWS Region. You can use AWS Direct Connect or an internet connection for the service link. This minimum enables you to launch EC2 instances, attach EBS volumes, and access AWS services, such as Amazon EKS, Amazon EMR, and CloudWatch metrics. +For an optimal experience and resiliency, AWSrecommends that you use redundant connectivity of at least 500 Mbps (1 Gbps is better) for the service link connection to the AWS Region. You can use Direct Connect or an internet connection for the service link. This minimum enables you to launch EC2 instances, attach EBS volumes, and access AWS services, such as Amazon EKS, Amazon EMR, and CloudWatch metrics.