aws-network-monitoring

Installs, configures, and troubleshoots CloudWatch Network Flow Monitor agents on EC2 instances.

2.5k|282|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-network-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-network-monitoring
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/operations-skills/aws-network-monitoring
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-network-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Setting up Amazon CloudWatch Network Flow Monitor agents on EC2 involves multiple error-prone steps: IAM policy attachment, SSM Distributor installation, agent activation, and diagnosing failures like HTTP 403 errors or missing metrics. This Skill provides the exact procedures and fixes so agents publish network latency and packet loss metrics correctly.

Core Features & Use Cases

  • Agent Installation: Install Network Flow Monitor agents via SSM Distributor (targeting instances by ID or tag) or via command-line package installs for Amazon Linux, Debian/Ubuntu, RHEL, and SUSE.
  • IAM Permission Setup: Attach the CloudWatchNetworkFlowMonitorAgentPublishPolicy managed policy to EC2 instance roles so agents can publish metrics.
  • Troubleshooting: Diagnose and fix common failures including HTTP 403 permission errors, agents never activated after SSM install, and connectivity issues to the networkflowmonitorreports endpoint.
  • Use Case: You need to monitor network path health between workloads across 50 EC2 instances. Use this Skill to install agents by tag via SSM, activate them, and verify HTTP 200 responses in the agent logs.

Quick Start

Install and activate the Network Flow Monitor agent on my EC2 instances using SSM Distributor, then verify it is publishing metrics.

Frequently Asked Questions about aws-network-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install the Network Flow Monitor agent on EC2 instances?

Use SSM Distributor with the AWS-ConfigureAWSPackage document and the AmazonCloudWatchNetworkFlowMonitorAgent package name, targeting instances by ID or tag. Alternatively, install the RPM or DEB package directly via yum or apt-get when SSM is unavailable.

What IAM policy does the Network Flow Monitor agent need?

Attach the AWS managed policy CloudWatchNetworkFlowMonitorAgentPublishPolicy to the EC2 instance role. Without it, the agent installs successfully but cannot publish metrics, resulting in HTTP 403 errors in the agent logs.

Why is my Network Flow Monitor agent not publishing metrics?

Common causes are a missing IAM publish policy (HTTP 403), the agent never being activated after an SSM Distributor install, or no network route to the networkflowmonitorreports endpoint. Check agent logs with journalctl -u network-flow-monitor.service for HTTP status codes.

Does the Network Flow Monitor agent work in private subnets?

Yes, but the instance needs a network path to the service endpoint. Prefer VPC endpoints for SSM and the Network Flow Monitor service over a NAT gateway to keep traffic on the AWS network.

Does the Network Flow Monitor agent support Windows?

No, Windows is not supported. The agent supports specific Linux distributions, kernel versions, and architectures including x86_64 and ARM64 (Graviton), as listed in the AWS documentation.