AWS vpc documentation change
Summary
Removed notes about shared resource requirements and transit gateway route table limitations.
Security assessment
The removed content relates to operational limitations and cross-account resource handling, but there is no evidence of a security vulnerability being addressed or new security documentation added.
Diff
diff --git a/vpc/latest/reachability/how-reachability-analyzer-works.md b/vpc/latest/reachability/how-reachability-analyzer-works.md index 46826e41b..a0dc0525e 100644 --- a//vpc/latest/reachability/how-reachability-analyzer-works.md +++ b//vpc/latest/reachability/how-reachability-analyzer-works.md @@ -137,2 +136,0 @@ Consider the following when working with Reachability Analyzer: - * Reachability Analyzer supports shared resources only if they can be fully described by the calling principal. For example, if a route references a prefix list owned by another account, the owner must share the prefix list with the calling principal for the analysis to succeed. - @@ -147,2 +144,0 @@ Consider the following when working with Reachability Analyzer: - * Reachability Analyzer can find paths through at most two transit gateway route tables. To analyze paths through additional transit gateway route tables, use Route Analyzer. For more information, see [Route Analyzer](https://docs.aws.amazon.com/network-manager/latest/tgwnm/route-analyzer.html) in the _Amazon VPC Transit Gateways_ guide. -