AWS prescriptive-guidance documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' in service link documentation, image captions, and Local Zones connectivity sections
Security assessment
Changes are branding/naming updates only (removing 'AWS' prefix from Direct Connect references). No security vulnerabilities, configurations, or features were modified or added. The encrypted VPN and MTU requirements remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/hybrid-cloud-best-practices/networking.md b/prescriptive-guidance/latest/hybrid-cloud-best-practices/networking.md index 21e65f49c..ce10f8ec0 100644 --- a//prescriptive-guidance/latest/hybrid-cloud-best-practices/networking.md +++ b//prescriptive-guidance/latest/hybrid-cloud-best-practices/networking.md @@ -46 +46 @@ When you design a hybrid architecture by using services such as Local Zones and -AWS Outposts provides a networking construct called a _service link_. The service link is a required connection between AWS Outposts and the selected AWS Region or parent Region (also referred to as _home Region_). It enables the management of the Outpost and the exchange of traffic between the Outpost and AWS Region. The service link uses an encrypted set of VPN connections to communicate with the home Region. You must provide connectivity between AWS Outposts and the AWS Region either through an internet link or an AWS Direct Connect public virtual interface (public VIF), or through an AWS Direct Connect private virtual interface (private VIF). For an optimal experience and resiliency, AWS recommends that you use redundant connectivity of at least 500 Mbps (1 Gbps is better) for the service link connection to the AWS Region. The minimum 500 Mbps service link connection allows you to launch Amazon EC2 instances, attach Amazon EBS volumes, and access AWS services such as Amazon EKS, Amazon EMR, and Amazon CloudWatch metrics. The network must support a maximum transmission unit (MTU) of 1,500 bytes between the Outpost and the service link endpoints in the parent AWS Region. For more information, see [AWS Outposts connectivity to AWS Regions](https://docs.aws.amazon.com/outposts/latest/userguide/region-connectivity.html) in the Outposts documentation[.](https://docs.aws.amazon.com/outposts/latest/userguide/region-connectivity.html) +AWS Outposts provides a networking construct called a _service link_. The service link is a required connection between AWS Outposts and the selected AWS Region or parent Region (also referred to as _home Region_). It enables the management of the Outpost and the exchange of traffic between the Outpost and AWS Region. The service link uses an encrypted set of VPN connections to communicate with the home Region. You must provide connectivity between AWS Outposts and the AWS Region either through an internet link or an Direct Connect public virtual interface (public VIF), or through an Direct Connect private virtual interface (private VIF). For an optimal experience and resiliency, AWS recommends that you use redundant connectivity of at least 500 Mbps (1 Gbps is better) for the service link connection to the AWS Region. The minimum 500 Mbps service link connection allows you to launch Amazon EC2 instances, attach Amazon EBS volumes, and access AWS services such as Amazon EKS, Amazon EMR, and Amazon CloudWatch metrics. The network must support a maximum transmission unit (MTU) of 1,500 bytes between the Outpost and the service link endpoints in the parent AWS Region. For more information, see [AWS Outposts connectivity to AWS Regions](https://docs.aws.amazon.com/outposts/latest/userguide/region-connectivity.html) in the Outposts documentation[.](https://docs.aws.amazon.com/outposts/latest/userguide/region-connectivity.html) @@ -48 +48 @@ AWS Outposts provides a networking construct called a _service link_. The servic - + @@ -50 +50 @@ AWS Outposts provides a networking construct called a _service link_. The servic -For information about creating resilient architectures for service links that use AWS Direct Connect and the public internet, see the [Anchor connectivity](https://docs.aws.amazon.com/whitepapers/latest/aws-outposts-high-availability-design/anchor-connectivity.html) section in the AWS whitepaper _AWS Outposts High Availability Design and Architecture Considerations_. +For information about creating resilient architectures for service links that use Direct Connect and the public internet, see the [Anchor connectivity](https://docs.aws.amazon.com/whitepapers/latest/aws-outposts-high-availability-design/anchor-connectivity.html) section in the AWS whitepaper _AWS Outposts High Availability Design and Architecture Considerations_. @@ -78 +78 @@ Amazon EC2 in Region | Amazon EC2 in Local Zones | 1,300 bytes -AWS Direct Connect | Local Zones | 1,468 bytes +Direct Connect | Local Zones | 1,468 bytes @@ -127 +127 @@ For more information, see [Connectivity options for Local Zones](https://docs.aw -### Local Zones and AWS Direct Connect +### Local Zones and Direct Connect @@ -129 +129 @@ For more information, see [Connectivity options for Local Zones](https://docs.aw -Local Zones also support AWS Direct Connect, which lets you route your traffic over a private network connection. For more information, see [Direct Connect in Local Zones](https://docs.aws.amazon.com/local-zones/latest/ug/local-zones-connectivity-direct-connect.html) in the Local Zones documentation. +Local Zones also support Direct Connect, which lets you route your traffic over a private network connection. For more information, see [Direct Connect in Local Zones](https://docs.aws.amazon.com/local-zones/latest/ug/local-zones-connectivity-direct-connect.html) in the Local Zones documentation.