CloudWatch Network Health Now Sees Across Transit Gateway Inter-Region Peering!
Hi, it's me, Shiichan! Today's news makes network troubleshooting a little easier.
AWS What's New
aws.amazon.com
What was announced?
AWS What's New announced that synthetic monitors in Amazon CloudWatch Network Monitoring now support paths that cross an AWS Transit Gateway (TGW) inter-Region peering connection, letting you determine whether a network performance issue on that path is caused by the AWS network.
The story so far
Previously, the network health indicator (NHI) for synthetic monitors only covered paths that go through AWS Direct Connect. For paths relying on Transit Gateway inter-Region peering, there was no way to tell whether degraded performance was coming from AWS's side or somewhere else.
What changes
This expansion adds NHI support for paths that reach a destination in a peered Region over Transit Gateway inter-Region peering.
- The indicator reflects the health of the AWS network path up to the Transit Gateway peering connection
- It's published to your own Amazon CloudWatch account, so you can build dashboards and set alarms on it
- Network operators and application developers can cut the time spent isolating the source of degradation
Dive Deep
This means teams running network setups that span regions can quickly tell whether the AWS-managed portion of the path is the likely culprit when performance issues show up. For the full list of supported regions, check the Regions list in the Amazon CloudWatch Network Monitoring documentation.
Wrap-up
- Synthetic monitors in Amazon CloudWatch Network Monitoring now cover paths over Transit Gateway inter-Region peering.
- Previously, only Direct Connect paths were covered.
- The network health indicator publishes to your CloudWatch account for dashboards and alarms.
- A useful time-saver for teams operating cross-region network setups who need to isolate the source of degradation quickly.
