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.