AWS vpc documentation change
Summary
Updated documentation to mention exclusion of intermediate components and added cross-reference
Security assessment
Minor clarification about existing functionality without introducing new security context. Changes are explanatory rather than addressing security concerns.
Diff
diff --git a/vpc/latest/reachability/how-reachability-analyzer-works.md b/vpc/latest/reachability/how-reachability-analyzer-works.md index 38ebc13ea..46826e41b 100644 --- a//vpc/latest/reachability/how-reachability-analyzer-works.md +++ b//vpc/latest/reachability/how-reachability-analyzer-works.md @@ -13 +13 @@ To use Reachability Analyzer, you specify the path for the traffic from a source -If there are multiple reachable paths between a source and a destination, Reachability Analyzer identifies and displays the shortest path. You can analyze the path again, specifying an intermediate component, to find an alternative reachable path that traverses the intermediate component. +If there are multiple reachable paths between a source and a destination, Reachability Analyzer identifies and displays the shortest path. You can analyze the path again, specifying or excluding an intermediate component, to find an alternative reachable path that traverses the intermediate component. @@ -63 +63 @@ In addition, Reachability Analyzer supports IP addresses as destinations. -Reachability Analyzer supports the following resource types as intermediate components: +Reachability Analyzer supports the following resource types as intermediate components. Specific intermediate components can be included or excluded from analysis when you're creating a path to analyse. See [Getting started with Reachability Analyzer](./getting-started.html) for more information. @@ -69 +69 @@ Reachability Analyzer supports the following resource types as intermediate comp - * Network Firewall firewall + * AWS Network Firewall