AWS outposts documentation change
Summary
Added documentation about VIF/VIF groups, route table associations, and routing domains. Updated links and clarified data plane path descriptions.
Security assessment
Changes focus on architectural components and connectivity workflows without mentioning security vulnerabilities, mitigations, or security-specific features. The additions explain networking constructs rather than addressing security risks.
Diff
diff --git a/outposts/latest/network-userguide/outposts-local-gateways.md b/outposts/latest/network-userguide/outposts-local-gateways.md index 8264c815c..06afad1dd 100644 --- a//outposts/latest/network-userguide/outposts-local-gateways.md +++ b//outposts/latest/network-userguide/outposts-local-gateways.md @@ -22,0 +23,2 @@ The local gateway is a core component of the architecture for your Outposts rack + * [VIF and VIF groups](./vif-vif-groups.html) + @@ -38 +40 @@ A local gateway has the following components: - * Route tables – Only the owner of a local gateway can create local gateway route tables. For more information, see [Local gateway route table routes](https://docs.aws.amazon.com/outposts/latest/network-userguide/manage-lgw-routes.html). + * Route tables – Only the owner of a local gateway can create local gateway route tables. For more information, see [Local gateway route table routes](./manage-lgw-routes.html). @@ -41,0 +44,6 @@ A local gateway has the following components: + * Local gateway virtual interfaces (VIFs) and VIF groups – Local gateway VIFs is a logical interface component of Outposts racks that sets up VLAN, IP, and BGP connectivity between an Outposts networking device and an on-premise networking device for local gateway connectivity. VIF groups are logical groupings of VIFs. You must create four local gateway VIFs within each VIF group for second-generation Outposts racks. + + * Local gateway route table and VPC associations – Local gateway route table and VPC associations allow you to connect your VPCs to local gateway route tables. With this association, you can add a route targeted to the local gateway within your Outposts subnet route table. This enables communication between your Outposts subnet resources and your on-premises network through the local gateway. + + * Local gateway routing domains – A local gateway routing domain is the association of a local gateway route table and local gateway VIF group. With this association, you can add a route targeted to a local gateway VIF group within your local gateway route table. This enables communication between your Outposts subnet resources and your on-premises network through the selected VIF group. + @@ -53,2 +60,0 @@ When AWS provisions your second-generation Outposts rack, we create some compone - * Creates the VIF and VIF groups. - @@ -63,0 +70,4 @@ When AWS provisions your second-generation Outposts rack, we create some compone + * Create the local gateway VIF and VIF groups. + + * Associate a local gateway route table with a local gateway VIF group to create a local gateway routing domain. + @@ -73 +83 @@ The instances in your Outpost subnet can use one of the following options for co - * Customer-owned IP addresses – The local gateway performs network address translation (NAT) for the customer-owned IP addresses that you assign to the instances in the Outpost subnet. This option supports overlapping CIDR ranges and other network topologies. + * Customer-owned IP addresses – The local gateway performs network address translation (NAT) for the customer-owned IP addresses that you assign to the instances in the Outpost subnet. This option supports overlapping CIDR ranges and other network topologies. For more information, see [Customer-owned IP addresses](https://docs.aws.amazon.com/outposts/latest/network-userguide/routing.html#ip-addressing). @@ -82 +92 @@ The primary role of a local gateway is to provide connectivity from an Outpost t -The local gateway can also provide a data plane path back to the AWS Region. The data plane path for the local gateway traverses from the Outpost, through the local gateway, and to your private local gateway LAN segment. It would then follow a private path back to the AWS service endpoints in the Region. Note that the control plane path always uses the service link connectivity, regardless of the data plane path that you use. +The data plane path for the local gateway traverses from the Outpost, through the local gateway, and to your private local gateway LAN segment. The local gateway can also provide a data plane path back to the AWS Region, for example for AWS service endpoints in the Region. Note that the control plane path always uses the service link connectivity, regardless of the data plane path that you use.