Set up alarms to be notified when your AWS resources exceed defined thresholds. Alarms can be configured at a group level or directly on individual monitored resources.
Cloudmon alarm rules work on a trigger model — you define a condition (the IF) and an action (the THEN). When the condition is met for the specified number of consecutive intervals, Cloudmon fires the alarm and executes the configured actions, such as sending a notification or running a script.
There are two ways to configure alarm rules for AWS resources:
Below are recommended alarm configurations for the most common AWS monitoring scenarios:
| Use Case | Metric | Suggested Threshold | Why |
| EC2 high CPU | CPU Utilisation | Above 90% for 1 interval | Catches instances under sustained heavy load before performance degrades |
| EC2 instance down | Status Check Failed | Above 0 for 1 interval | Immediately alerts when an instance fails a health check |
| RDS low storage | Free Storage Space | Below 10% for 1 interval | Prevents database outages caused by running out of disk space |
| RDS high connections | Database Connections | Above limit for 2 intervals | Detects connection leaks or unusual application behaviour early |
| EC2 unexpected reboot | System Reboot | Is detected | Flags unplanned reboots that could indicate instability or unauthorised activity |
| EC2 high network traffic | Network In / Network Out | Above expected baseline | Identifies unusual traffic spikes that could indicate a security issue or misconfigured application |
Once saved, all triggers for a resource are listed in the Triggers table under the Alarm Rule section. Each row shows the trigger title, alarm severity, whether notifications are configured, and whether a script is set to run. You can edit or delete any trigger at any time using the action icons on the right.