Freedom251 › Mobile App Monitoring
AWS Network Synthetic Monitor
What AWS Network Synthetic Monitor is
AWS Network Synthetic Monitor shows network performance between applications hosted on AWS and destinations on premises. It continuously measures packet loss and latency across hybrid connections, helping network operators and application developers locate degradation within minutes. AWS manages the monitoring probes, so agents do not have to be installed on VPCs or on-premises resources. For paths using Direct Connect or Transit Gateway inter-Region peering, a binary network health indicator—0 or 100—helps indicate whether the problem is within AWS. Metrics are published to CloudWatch Metrics for dashboards, thresholds, and alarms, and private connectivity is available through AWS PrivateLink. On-premises destinations can use IPv4 or IPv6 addresses. Each monitored subnet resource supports up to four probes for four destination IP addresses. Pricing starts at $0.10 per monitored resource per hour, with separate CloudWatch metric charges and no upfront or long-term commitment.
Who it suits
It suits network operators and application developers needing real-time visibility into hybrid AWS network performance. It is also relevant to teams using Direct Connect or Transit Gateway paths.
What it does well
- Continuously measures packet loss and latency
- AWS manages monitoring probes
- CloudWatch dashboards, thresholds, and alarms
- Supports IPv4 and IPv6 destinations
- Private connectivity through AWS PrivateLink
What to know first
- No free plan
- No automatic network failover
- Up to four probes per subnet resource
- CloudWatch metrics are charged separately
Limits
Each monitored subnet resource supports up to four probes covering four destination IP addresses. Pricing also includes separate CloudWatch metrics fees, and the service does not automatically fail over during an AWS network issue.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Pay as you go | Hourly per monitored resource; CloudWatch metrics charged separately · $0.10 per monitored resource per hour in the example · each resource covers four on-premises IP addresses by default · standard CloudWatch metrics pricing applies | $0.10 a month |
| Pay-as-you-go Network Synthetic Monitor | hourly per monitored resource; CloudWatch metrics billed separately · $0.10 per monitored resource-hour in US East example · 4 destination IPs per subnet included by default · additional probes and metrics charged | $0.10 a month |
As docs.aws.amazon.com lists them, read 4 Oct 2026. The maker's own page has the final word.
Getting started
- Open the Network Synthetic Monitor documentation website
- Choose the Pay as you go plan
- Use the AWS web interface or API
- Select a monitored AWS subnet resource
- Specify up to four destination IP addresses
- Connect CloudWatch Metrics for dashboards, thresholds, or alarms
Verdict
AWS Network Synthetic Monitor focuses on continuous visibility and pinpointing degradation across AWS and on-premises paths. Its managed probes and CloudWatch integration reduce setup work, while the lack of automatic failover means it monitors problems rather than correcting them.
Questions
How is Network Synthetic Monitor priced?
The Pay as you go plan is $0.10 a month, billed hourly per monitored resource. CloudWatch metrics are charged separately, with no upfront costs or long-term commitments.
Is there a free plan?
No. AWS lists the service as paid.
Which platforms can I use?
Access is available through API and web interfaces.
What does it measure?
It continuously tracks packet loss and latency for hybrid network connections between AWS applications and on-premises destinations.
How many probes can a monitored subnet use?
Each monitored subnet resource can have up to four probes for traffic to four destination IP addresses.
Does it provide automatic network failover?
No. The service does not automatically fail over when an AWS network issue occurs.
Facts from AWS Network Synthetic Monitor's own pages
- Access security
- API clients must use TLS 1.0 or later, with TLS 1.2 or later recommended, and sign requests using IAM-associated credentials or temporary AWS STS credentials. · docs.aws.amazon.com, 4 Oct 2026
- Account requirement
- Monitor source subnets must belong to the same AWS account as the monitor. · docs.aws.amazon.com, 15 Oct 2026
- Agentless and PrivateLink
- No agents are installed in VPCs or on-premises; AWS PrivateLink can provide a private connection to the monitoring resources. · docs.aws.amazon.com, 15 Oct 2026
- Audience
- It is intended for network operators and application developers seeking real-time network performance insights. · docs.aws.amazon.com, 4 Oct 2026
- AWS health indicator
- The network health indicator helps diagnose whether degradation is within AWS for paths through Direct Connect or Transit Gateway inter-Region peering, and its metric is binary, 0 or 100. · docs.aws.amazon.com, 4 Oct 2026
- CloudWatch integration
- Probe metrics feed CloudWatch Metrics, where users can build dashboards, thresholds and alarms. · docs.aws.amazon.com, 15 Oct 2026
- Company history
- AWS says it launched in 2006. · aws.amazon.com, 4 Oct 2026
- Connectivity integrations
- AWS describes hybrid monitoring for Direct Connect and Site-to-Site VPN, with alarms that can connect to SNS, EventBridge and Lambda workflows. · aws.amazon.com, 15 Oct 2026
- Continuous metrics
- The service continuously benchmarks hybrid paths with real-time packet-loss and latency measurements. · docs.aws.amazon.com, 15 Oct 2026
- Data protection
- AWS recommends least-privilege IAM, MFA, CloudTrail, TLS 1.2, encryption and FIPS endpoints, and warns against placing secrets in tags, names or destination URLs. · docs.aws.amazon.com, 15 Oct 2026
- IAM requirements
- Viewing requires CloudWatch metric-data access plus networkmonitor Get and List permissions; creation also needs service-linked-role, EC2 interface and security-group permissions. · docs.aws.amazon.com, 15 Oct 2026
- IP support
- On-premises destinations support IPv4 and IPv6 addresses. · docs.aws.amazon.com, 4 Oct 2026
- Limit: Capterra reviewers
- Capterra reviewers cite a steep learning curve, difficult log navigation and confusing or escalating costs. · capterra.com, 15 Oct 2026
- Limit: cost alternative
- The same experiment concluded self-built EC2 scripts can be more economical for noncritical or development monitoring. · dev.classmethod.jp, 15 Oct 2026
- Limit: destinations
- Reserved or AWS-internal addresses such as 169.254.0.0/16 and 10.0.0.2 produce invalid path measurements and should not be used. · docs.aws.amazon.com, 15 Oct 2026
- Limit: failover
- The service does not automatically fail over network traffic when AWS has a network problem. · docs.aws.amazon.com, 15 Oct 2026
- Limit: G2 reviewers
- G2 reviewers repeatedly mention a complex interface, difficult log queries and costs that increase with high-volume logs or custom metrics. · g2.com, 15 Oct 2026
- Limit: probe cost
- DevelopersIO reported probe pricing of about $0.11 per subnet-hour plus CloudWatch metrics and described the probe cost as expensive. · dev.classmethod.jp, 15 Oct 2026
- Limit: public IP paths
- A DevelopersIO experiment found probes cannot reach global IPs directly because their ENIs have no public IP, requiring NAT Gateway or public addressing. · dev.classmethod.jp, 15 Oct 2026
- Maker and ownership
- Amazon Web Services, Inc. is an Amazon.com, Inc. business segment, launched in 2006 and headquartered in Seattle, Washington. · aws.amazon.com, 15 Oct 2026
- Managed operation
- AWS fully manages monitoring probes, so separate agents do not need to be installed on VPCs or on-premises resources. · docs.aws.amazon.com, 4 Oct 2026
- Measurements
- It tracks continuous packet loss and latency for hybrid network connections. · docs.aws.amazon.com, 4 Oct 2026
- Network health indicator
- Its Network Health Indicator is a binary 0-or-100 CloudWatch metric estimating whether degradation is inside AWS on eligible Direct Connect or Transit Gateway inter-Region paths. · docs.aws.amazon.com, 15 Oct 2026
- Notable limitation
- The service does not provide automatic network failover if an AWS network issue occurs. · docs.aws.amazon.com, 4 Oct 2026
Where AWS Network Synthetic Monitor stands on Freedom251
- Mobile App Monitoring#20 of 23