AWS AmazonCloudWatch documentation change
Summary
Changed terminology from 'enable' to 'initialize' regarding Network Flow Monitor role creation process
Security assessment
The change clarifies the activation process terminology but does not address security vulnerabilities or document security features.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/using-service-linked-roles-network-flow-monitor.md b/AmazonCloudWatch/latest/monitoring/using-service-linked-roles-network-flow-monitor.md index 25410979c..494815855 100644 --- a//AmazonCloudWatch/latest/monitoring/using-service-linked-roles-network-flow-monitor.md +++ b//AmazonCloudWatch/latest/monitoring/using-service-linked-roles-network-flow-monitor.md @@ -60 +60 @@ The **AWSServiceRoleForNetworkFlowMonitor_Topology** service-linked role trusts -You do not need to manually create the service-linked roles for Network Flow Monitor. The first time that you enable Network Flow Monitor, Network Flow Monitor creates **AWSServiceRoleForNetworkFlowMonitor** and **AWSServiceRoleForNetworkFlowMonitor_Topology** for you. +You do not need to manually create the service-linked roles for Network Flow Monitor. The first time that you initialize Network Flow Monitor, Network Flow Monitor creates **AWSServiceRoleForNetworkFlowMonitor** and **AWSServiceRoleForNetworkFlowMonitor_Topology** for you.