Network Synthetic Monitor
Fully managed, agentless synthetic monitoring for hybrid and cross-region AWS network paths — detect grey failures in minutes, not hours.
What is Network Synthetic Monitor? ▾
Amazon CloudWatch Network Synthetic Monitor is a fully managed feature of CloudWatch that provides continuous, synthetic network path monitoring. It sends active probe traffic from your VPC subnets to destinations — on-premises IPs (via Direct Connect or Site-to-Site VPN) or cross-region PrivateLink endpoints — and publishes real-time round-trip time (RTT) and packet loss metrics.
It requires no agents to install or maintain. You simply specify source subnets and destination IPs, and AWS provisions all necessary infrastructure (ENIs and probe instances) in the background.
Problems It Addresses ▾
| Problem | Description |
|---|---|
| Grey Failures | Intermittent packet loss or fluctuating latency that the routing control plane (BGP) doesn't detect — but your applications suffer from reduced throughput and increased latency. |
| High MTTR | When a network issue occurs, engineers spend significant time determining where the problem is — is it the AWS network, the Direct Connect partner backbone, or the on-premises network? |
| BGP Blind Spots | BGP uses TCP which tolerates degradation via retransmissions. A link can be dropping packets while BGP sessions remain up, leaving you unaware of the problem. |
| DIY Monitoring Overhead | Before Network Synthetic Monitor, teams had to build and maintain custom probe agents, EC2 instances running ping/traceroute scripts, or purchase third-party solutions. |
| Cross-Region Path Blindness | PrivateLink cross-region traffic traverses the AWS backbone, but without active probing there's no way to detect path-specific degradations between regions. |
| Multi-AZ Visibility Gaps | Workloads in different Availability Zones may experience different network conditions. Traditional monitoring doesn't differentiate per-AZ network paths. |
How Network Synthetic Monitor Solves These Issues ▾
| Solution | Description |
|---|---|
| Continuous active probing | Sends synthetic ICMP/TCP probes every 30–60 seconds from your subnets to your destinations — surfacing packet loss and latency spikes that BGP and passive monitoring miss. |
| Network Health Indicator (NHI) | For Direct Connect paths, NHI uses anomaly detection to report whether degradation is within the AWS-controlled network (value = 1) or elsewhere (value = 0), dramatically reducing time to locate the fault. |
| Per-AZ, per-path granularity | Deploy probes in each subnet/AZ to monitor specific network paths independently. Network engineers can correlate failures to individual DX connections or VPN tunnels. |
| Zero operational overhead | AWS provisions and maintains all probe infrastructure (ENIs, instances). No agents to install, patch, or scale. ENI IP addresses persist even if a probe instance is replaced. |
| Native CloudWatch integration | Metrics flow directly into CloudWatch. Set static thresholds or use anomaly detection. Trigger automated failover via EventBridge + Lambda when degradation is detected. |
| Cross-region PrivateLink monitoring | Probe PrivateLink interface endpoint IPs across regions using TCP, measuring the actual path your traffic takes across the AWS backbone. |
Architecture Diagram ▾
The following diagram illustrates a network engineer's monitoring architecture using Network Synthetic Monitor with a Direct Connect High Resiliency setup. Probes are deployed in monitoring subnets across two Availability Zones, each targeting separate on-premises destinations reachable via distinct DX connections — enabling per-path fault isolation.
How It Works ▾
Step 1: Create a Monitor
Define a monitor specifying: aggregation interval (30 or 60 seconds), source VPC subnets, destination IPs, protocol (ICMP or TCP), port, and packet size.
Step 2: AWS Provisions Infrastructure
AWS creates managed probe instances and attaches customized ENIs to your specified subnets. Each source + destination + protocol + packet size combination is a "probe."
Step 3: Active Probes Transmit
ICMP: Sends echo requests, expects echo replies. TCP: Sends SYN packets, expects SYN+ACK. Periodically rotates source ports (1024–65535) for broader path coverage.
Step 4: Metrics Published to CloudWatch
Every aggregation interval, three metrics per probe are published under AWS/NetworkMonitor: RTT (μs), PacketLoss (%), and HealthIndicator (0 or 1).
Step 5: Alert & Automate
Configure CloudWatch Alarms (static thresholds or anomaly detection). Integrate with SNS for notifications or EventBridge + Lambda for automated failover actions.
Supported Protocols
| Protocol | Mechanism | Use Case | Notes |
|---|---|---|---|
ICMP | Echo Request → Echo Reply | Hybrid paths (DX, VPN) | 56 bytes default packet size |
TCP | SYN → SYN+ACK | PrivateLink, service-port monitoring | Port range 1024-65535 rotated for coverage. Required for PrivateLink (ICMP not forwarded). |
Monitoring Use Cases
| Use Case | Description |
|---|---|
| Hybrid / Direct Connect | Monitor on-premises connectivity from VPC subnets. Use NHI to distinguish AWS-side vs. customer-side issues. |
| Site-to-Site VPN | Detect tunnel degradation that BGP sessions mask. Alert before application impact. |
| Cross-Region PrivateLink | Probe interface endpoint IPs across regions with TCP. Detect backbone latency or loss on your critical service paths. |
| Automated Failover | Pair alarms with Lambda to automatically reroute traffic when a path becomes impaired. |
Key Metrics ▾
Network Synthetic Monitor publishes the following metrics under the AWS/NetworkMonitor namespace at configurable intervals:
- RTT (μs) — Round-trip time in microseconds
- PacketLoss (%) — Percentage of probes that did not receive a response
- HealthIndicator (0 or 1) — For Direct Connect paths, indicates whether degradation is on the AWS side (1 = AWS issue detected)