AWS prescriptive-guidance documentation change
Summary
Updated image paths for architecture diagrams and removed external documentation link reference
Security assessment
Changes only affect image locations and remove a hyperlink to Local Zones documentation. No security-related content modifications are present.
Diff
diff --git a/prescriptive-guidance/latest/hybrid-cloud-best-practices/networking.md b/prescriptive-guidance/latest/hybrid-cloud-best-practices/networking.md index 4a5122ad0..2043a28e1 100644 --- a//prescriptive-guidance/latest/hybrid-cloud-best-practices/networking.md +++ b//prescriptive-guidance/latest/hybrid-cloud-best-practices/networking.md @@ -40 +40 @@ The following diagram shows an AWS architecture that includes Outpost and Local - + @@ -50 +50 @@ AWS Outposts provides a networking construct called a _service link_. The servic - + @@ -99 +99 @@ The local gateway (LGW) is a core component of the AWS Outposts architecture. Th - + @@ -106 +106 @@ The local gateway (LGW) is a core component of the AWS Outposts architecture. Th - + @@ -112 +112 @@ Local connectivity from AWS Outposts to a local network requires some parameter -Industries that require low-latency or local data residency (examples include gaming, live streaming, financial services, and the government) can use Local Zones to deploy and provide their applications to end users over the internet. During the deployment of a Local Zone, you must allocate public IP addresses for use in a Local Zone. When you allocate Elastic IP addresses, you can specify the location from which the IP address is advertised. This location is called a _network border group_. A network border group is a collection of Availability Zones, Local Zones, or AWS Wavelength Zones from which AWS advertises a public IP address. This helps ensure minimum latency or physical distance between the AWS network and the users who access the resources in these Zones. To see all the network border groups for Local Zones, see [Available Local Zones](https://docs.aws.amazon.com/local-zones/latest/ug/available-local-zones.html) in the Local Zones documentation. +Industries that require low-latency or local data residency (examples include gaming, live streaming, financial services, and the government) can use Local Zones to deploy and provide their applications to end users over the internet. During the deployment of a Local Zone, you must allocate public IP addresses for use in a Local Zone. When you allocate Elastic IP addresses, you can specify the location from which the IP address is advertised. This location is called a _network border group_. A network border group is a collection of Availability Zones, Local Zones, or AWS Wavelength Zones from which AWS advertises a public IP address. This helps ensure minimum latency or physical distance between the AWS network and the users who access the resources in these Zones.