AWS outposts documentation change
Summary
Updated phrasing from 'will cause' to 'may cause' regarding BGP conflicts and removed redundant notes.
Security assessment
The change softens language about network misconfiguration consequences but does not introduce or modify security controls. No evidence of addressing a security vulnerability or documenting new security features.
Diff
diff --git a/outposts/latest/network-userguide/private-connectivity.md b/outposts/latest/network-userguide/private-connectivity.md index 3ad72759f..688279aee 100644 --- a//outposts/latest/network-userguide/private-connectivity.md +++ b//outposts/latest/network-userguide/private-connectivity.md @@ -25 +25 @@ Second-generation Outposts racks require a larger subnet size (/24 or larger) an -When configuring private connectivity for the Outposts service link, plan your IP addressing carefully to avoid future conflicts. Service Link VIFs are immutable. You cannot create CoIP pools or DVR subnet ranges assigned to the Local Gateway (LGW) that overlap with existing Service Link address ranges or VPC CIDR ranges used for the dedicated private connectivity VPC, as they will cause BGP routing conflicts and affect Service Link functionality. +When configuring private connectivity for the Outposts service link, plan your IP addressing carefully to avoid future conflicts. Service Link VIFs are immutable. You should avoid creating CoIP pools or DVR subnet ranges assigned to the Local Gateway (LGW) that overlap with existing Service Link address ranges or VPC CIDR ranges used for the dedicated private connectivity VPC, as they may cause BGP routing conflicts and disrupt Service Link functionality. @@ -98,2 +97,0 @@ JSON -###### Note - @@ -119,2 +116,0 @@ After your Outpost is installed, confirm connectivity to the private IPs in your -###### Note -