Set up Network Flow Monitor agents on EC2 to track network latency and packet loss. Configure publishing permissions, verify agent operation, and troubleshoot missing metrics, HTTP 403 errors, or connectivity failures.
Installs, configures, and troubleshoots Network Flow Monitor agents on EC2 instances to monitor network path health. Covers agent installation, IAM permissions, monitoring network paths, and troubleshooting agents reporting no metrics, HTTP 403 errors, or connectivity failures.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Domain expertise for installing and configuring Amazon CloudWatch Network Flow Monitor agents on EC2 instances. Covers IAM permission setup, agent installation via SSM Distributor or command-line install, agent activation, verification, and troubleshooting.
Network Flow Monitor agents are lightweight software that publish performance metrics (latency, packet loss) to the Network Flow Monitor backend, enabling monitoring of network path health between workloads.
Works best with the AWS MCP server — enables running SSM commands, attaching IAM policies, and validating agent status directly. All guidance also works with standard AWS CLI access.
| User need | Action |
|---|---|
| Installing Network Flow Monitor agents on EC2 | Read agent-install-ec2.md |
| Configuring IAM for Network Flow Monitor agents | Read agent-permissions.md |
| Troubleshooting Network Flow Monitor agents (403, no metrics, connectivity) | Read troubleshooting.md |
| Spans multiple areas | Read the most specific reference first, then consult others as needed |
| File | Content |
|---|---|
| agent-install-ec2.md | End-to-end Network Flow Monitor agent installation via SSM Distributor, activation, verification |
| agent-permissions.md | IAM policy setup for Network Flow Monitor agent metric publishing |
| troubleshooting.md | Error → cause → fix for Network Flow Monitor agent issues (HTTP 403, missing metrics, connectivity) |
For supported Linux distributions, kernel versions, and architectures, see the AWS documentation. Windows is not supported.
CloudWatchNetworkFlowMonitorAgentPublishPolicy for publishing metrics and AmazonSSMManagedInstanceCore for SSM management. Do not use *FullAccess policies.com.amazonaws.<region>.ssm, .ssmmessages, .ec2messages) over a NAT gateway to keep traffic on the AWS network.SendCommand invocations and IAM AttachRolePolicy actions performed during agent setup are logged for security investigations.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Choose where to run an AI agent on AWS through a guided assessment. Develop an architecture and rough cost estimate, then optionally create a migration plan and executable proof of concept to test the proposed setup.
Extend an existing AgentCore agent with memory across sessions, app integration, browser access, code execution, payments, or collaboration between agents. The skill also guides private network setup, model changes, migration from Bedrock Agent, and resource removal.
Connect an AgentCore agent to external APIs, MCP servers, and Lambda tools through AgentCore Gateway. Configure credentials and outbound authentication, and use Cedar policies, rules that control which tools an agent may call.
Diagnose AgentCore agent failures by reading logs and traces, records of execution steps. Investigate wrong answers, tool errors, timeouts, and memory problems, or check environment prerequisites when the CLI itself fails.
Prepare and troubleshoot AgentCore deployments to AWS by checking configuration, permissions, and deployment changes. Diagnose common failures, choose deployment targets, and manage versions through rollback, version pinning, or canary deployments that gradually introduce a new version.
Create a new agent project on AWS with AgentCore. Get help choosing a framework, generating the project structure, running it locally, and completing the first deployment and invocation, with explanations of the generated files.