AWS AmazonCloudWatch documentation change
Summary
Updated installation/uninstallation procedures for Network Flow Monitor agents, added billing cost warnings for active agents, and clarified activation/deactivation processes
Security assessment
Changes focus on procedural clarifications and cost management aspects (billing warnings). No evidence of addressing vulnerabilities or security weaknesses. IAM role mentions are part of standard configuration rather than new security content
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-agents-ec2.md b/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-agents-ec2.md index 816e75b44..6889b69a2 100644 --- a/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-agents-ec2.md +++ b/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor-agents-ec2.md @@ -60 +60 @@ If an instance doesn't have an IAM role attached, choose a role by doing the fol -Network Flow Monitor provides a distributor package in AWS Systems Manager for you to install agents: **AmazonCloudWatchNetworkFlowMonitorAgent**. To access and run the package, follow the steps provided here. +Network Flow Monitor provides a distributor package in AWS Systems Manager for you to install Network Flow Monitor agents: **AmazonCloudWatchNetworkFlowMonitorAgent**. To access and run the package to install agents, follow the steps provided here. @@ -62 +62 @@ Network Flow Monitor provides a distributor package in AWS Systems Manager for y -###### To install agents for Network Flow Monitor +###### To install agents in EC2 instances @@ -66 +66 @@ Network Flow Monitor provides a distributor package in AWS Systems Manager for y - 2. Under **Owned by Amazon** , locate the Network Flow Monitor package: **AmazonCloudWatchNetworkFlowMonitorAgent**. + 2. Under **Owned by Amazon** , locate the Network Flow Monitor package, **AmazonCloudWatchNetworkFlowMonitorAgent** , and select it. @@ -68 +68 @@ Network Flow Monitor provides a distributor package in AWS Systems Manager for y - 3. After you select the package, choose **Install one time** or **Install on schedule**. + 3. Choose **Run command**. @@ -70 +70 @@ Network Flow Monitor provides a distributor package in AWS Systems Manager for y - 4. Select the EC2 instances to install agents on. For example, you can select instances based on tags, choose instances manually, or base the choice on resource groups. + 4. Choose **Install one time** or **Install on schedule**. @@ -72 +72 @@ Network Flow Monitor provides a distributor package in AWS Systems Manager for y - 5. Optionally, select where the output of the execution will be stored: Amazon S3 or Amazon CloudWatch. If an installation fails, you can go this location to get more information to help you troubleshoot. + 5. Select the EC2 instances to install agents on. For example, you can select instances based on tags, choose instances manually, or base the choice on resource groups. @@ -74 +74,5 @@ Network Flow Monitor provides a distributor package in AWS Systems Manager for y - 6. Choose **Run** to start the installation. + 6. For **Action** , choose **Install**. + + 7. Optionally, select where the output of the execution will be stored: Amazon S3 or Amazon CloudWatch. If an installation fails, you can go this location to get more information to help you troubleshoot. + + 8. Choose **Run** to start the installation. @@ -81 +85 @@ If the installation is successful and the instances have permissions to access N -If you no longer need agents, you can uninstall them. +Agents that are active (sending metrics data) incur billing costs. For more information about Network Flow Monitor and Amazon CloudWatch pricing, see Network Monitoring on the [Amazon CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/) page. If you don't need metrics data temporarily, you can deactivate an agent. For more information, see Activate or deactivate agents. If you no longer need Network Flow Monitor agents, you can uninstall them from the EC2 instances. @@ -83 +87 @@ If you no longer need agents, you can uninstall them. -###### To uninstall agents for Network Flow Monitor +###### To uninstall agents from EC2 instances @@ -87 +91 @@ If you no longer need agents, you can uninstall them. - 2. Under **Command document** , locate the Network Flow Monitor package: **AmazonCloudWatchNetworkFlowMonitorAgent**. + 2. Under **Command document** , locate the Network Flow Monitor package, **AmazonCloudWatchNetworkFlowMonitorAgent** , and select it. @@ -89 +93 @@ If you no longer need agents, you can uninstall them. - 3. For **Action** , choose **Uninstall**. + 3. Choose **Run command**. @@ -91 +95 @@ If you no longer need agents, you can uninstall them. - 4. Select the EC2 instances to uninstall agents from. + 4. For **Action** , choose **Uninstall**. @@ -93 +97,3 @@ If you no longer need agents, you can uninstall them. - 5. Choose **Run**. + 5. Select the EC2 instances to uninstall agents from. + + 6. Choose **Run**. @@ -100 +106,3 @@ If you no longer need agents, you can uninstall them. -Network Flow Monitor provides a document in AWS Systems Manager that you can use activate or deactivate agents that you've installed on your EC2 instances. You might want to deactivate agents, for example, if you don't want them to continue collecting metrics. By running this document to manage the agents, you can deactivate them (and then activate them again, if you choose) without uninstalling the agents. +After you install a Network Flow Monitor agent with SSM, you must activate it to receive network flow metrics from the instance where it's installed. Agents that are active (sending metrics data) incur billing costs. For more information about Network Flow Monitor and Amazon CloudWatch pricing, see Network Monitoring on the [Amazon CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/) page. If you don't need metrics data temporarily, you can deactivate an agent to prevent ongoing billing for the agent. + +Network Flow Monitor provides a document in AWS Systems Manager that you can use activate or deactivate agents that you've installed on your EC2 instances. By running this document to manage the agents, you can activate them to begin receiving performance metrics. Or, you can deactivate them to temporarily stop metrics from being sent,without uninstalling the agents. @@ -102 +110 @@ Network Flow Monitor provides a document in AWS Systems Manager that you can use -The document that you can use to activate or deactivate agents is called **AmazonCloudWatch-NetworkFlowMonitorManageAgent**. To access and run the document, follow the steps in the procedure. +The document in SSM that you can use to activate or deactivate agents is called **AmazonCloudWatch-NetworkFlowMonitorManageAgent**. To access and run the document, follow the steps in the procedure. @@ -108 +116 @@ The document that you can use to activate or deactivate agents is called **Amazo - 2. Under **Owned by Amazon** , locate the Network Flow Monitor document: **AmazonCloudWatch-NetworkFlowMonitorManageAgent** and select the document. + 2. Under **Owned by Amazon** , locate the Network Flow Monitor document, **AmazonCloudWatch-NetworkFlowMonitorManageAgent** , and select the document. @@ -110 +118 @@ The document that you can use to activate or deactivate agents is called **Amazo - 3. Select the EC2 instances to activate or deactivate agents on. For example, you can select instances based on tags, choose instances manually, or base the choice on resource groups. + 3. Choose **Run command**. @@ -112 +120 @@ The document that you can use to activate or deactivate agents is called **Amazo - 4. Optionally, select where the output of the execution will be stored: Amazon S3 or Amazon CloudWatch. If an activation or deactivation fails, you can go this location to get more information to help you troubleshoot. + 4. For **Action** , choose **Activate** or **Deactivate** , depending on the action that you want to be completed for the agents. @@ -114 +122 @@ The document that you can use to activate or deactivate agents is called **Amazo - 5. For **Action** , enter **Activate** or **Deactivate** , depending on the action that you want to be completed. + 5. Select the EC2 instances to activate or deactivate agents on. For example, you can select instances based on tags, choose instances manually, or base the choice on resource groups.