AWS network-firewall documentation change
Summary
Updated propagation time estimate for firewall changes from 'seconds' to 'minutes'
Security assessment
The change corrects timing expectations for configuration propagation but does not indicate a security fix. It reduces potential confusion but lacks evidence of addressing a security flaw.
Diff
diff --git a/network-firewall/latest/developerguide/rule-group-updating.md b/network-firewall/latest/developerguide/rule-group-updating.md index b7f49c090..13a052943 100644 --- a//network-firewall/latest/developerguide/rule-group-updating.md +++ b//network-firewall/latest/developerguide/rule-group-updating.md @@ -24 +24 @@ Follow the guidance in this section to change your rule group settings through t -When you make any changes to a firewall, including changes to any of the firewall's components, like rule groups, TLS inspection configurations, and firewall policies, Network Firewall propagates the changes everywhere that the firewall is used. Your changes are normally applied within seconds, but there might be a brief period of inconsistency when the changes have arrived in some places and not in others. For example, if you modify a rule group so that it drops an additional type of packet, for a firewall that uses the rule group, the new packet type might briefly be dropped by one firewall endpoint while still being allowed by another. +When you make any changes to a firewall, including changes to any of the firewall's components, like rule groups, TLS inspection configurations, and firewall policies, Network Firewall propagates the changes everywhere that the firewall is used. Your changes are normally applied within minutes, but there might be a brief period of inconsistency when the changes have arrived in some places and not in others. For example, if you modify a rule group so that it drops an additional type of packet, for a firewall that uses the rule group, the new packet type might briefly be dropped by one firewall endpoint while still being allowed by another.