AWS AmazonCloudWatch documentation change
Summary
Updated setup steps for Network Flow Monitor, including AWS Organizations integration for multi-account monitoring and restructured review process.
Security assessment
The changes clarify setup procedures and multi-account monitoring via AWS Organizations but do not address specific security vulnerabilities or introduce new security features. The mention of service-linked roles is part of standard AWS configuration.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-get-started.md b/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-get-started.md index 50528821b..6af47d38c 100644 --- a//AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-get-started.md +++ b//AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-get-started.md @@ -7 +7 @@ -To help you get started, the section provides an overview of the steps to configure and use and gain insights with Network Flow Monitor. The steps to follow are shown here, at a high level. For details, see the additional sections in this guide about configuring agents and monitors. +To help you get started, the section provides a high level overview of the steps to configure, and then gain insights, with Network Flow Monitor. For details, see the additional sections in this guide about initializing Network Flow Monitor, configuring agents, and creating monitors. @@ -9 +9 @@ To help you get started, the section provides an overview of the steps to config - * Enable Network Flow Monitor, to accept service-linked role permissions and create a _scope_ for monitoring in Network Flow Monitor. At this time, Network Flow Monitor sets the monitoring scope to the resources of the AWS account that you enable the feature with. To learn more about the managed policies that the service-linked roles use, see [AWS managed policies for Network Flow Monitor](./security-iam-awsmanpol-network-flow-monitor.html). + * Initialize Network Flow Monitor, to accept service-linked role permissions, create a _scope_ for monitoring in Network Flow Monitor, and create an initial topology. If you want to observe network performance for network flows for instances in multiple accounts, you must integrate with AWS Organizations, and then add the accounts to your scope. To learn more, see [Initialize Network Flow Monitor](./CloudWatch-NetworkFlowMonitor-configure-begin.html). @@ -17 +17 @@ To help you get started, the section provides an overview of the steps to config - * On a regular basis: Review network flow information in the monitors that you've created, to learn about and help troubleshoot network impairments in your workloads. + * On a regular basis: @@ -19 +19,3 @@ To help you get started, the section provides an overview of the steps to config - * On a regular basis: Review workload insights for the network flows that you're monitoring, to determine if the monitors that you've created are covering the most relevant network flows or if it would be helpful to create new monitors. + * Review network flow information in the monitors that you've created, to learn about and help troubleshoot network impairments in your workloads. + + * Review workload insights for the network flows that you're monitoring, to determine if the monitors that you've created are covering the most relevant network flows or if it would be helpful to create new monitors.