A VPN Gateway is considered non-compliant if its inbound bandwidth usage is greater than or equal to a specified value for at least 8 hours within a specific time range. This rule does not apply if the VPN Gateway is not connected to Cloud Monitor or if no monitoring data is available. By default, the detection period is the last 7 days. The check uses the monitoring data API of Cloud Monitor and consumes the free quota of basic Cloud Monitor. For better detection quality, you can enable Hybrid Cloud Monitoring. For more information about the billing of Hybrid Cloud Monitoring, see the billing documentation for Cloud Monitor.
Risk level
Default risk level: Medium.
You can change the risk level as needed.
Detection logic
A VPN Gateway is considered non-compliant if its inbound bandwidth usage is greater than or equal to a specified value for at least 8 hours within a specific time range. This rule does not apply if the VPN Gateway is not connected to Cloud Monitor or if no monitoring data is available. By default, the detection period is the last 7 days. The check uses the monitoring data API of Cloud Monitor and consumes the free quota of basic Cloud Monitor. For better detection quality, you can enable Hybrid Cloud Monitoring. For more information about the billing of Hybrid Cloud Monitoring, see the billing documentation for Cloud Monitor.
Rule details
Parameter | Description |
Rule name | Check the inbound bandwidth usage of a VPN Gateway |
Rule identifier | |
Tag | VPN |
Automatic remediation | Not supported |
Rule triggers | Periodic |
Trigger frequency | 24 hours |
Supported resource types | ACS::VPN::VpnGateway |
Input parameters | relativeTime (Default: 168) |