Monitor the availability, performance, and resource utilisation of your EC2 instances in real time. Cloudmon gives IT teams early visibility into issues before they impact operations.
EC2 (Elastic Compute Cloud) instances are virtual servers running in the AWS cloud. Once your AWS account is connected to Cloudmon, EC2 instances are auto-discovered.
Selecting an EC2 instance opens its detail page. The overview displays the instance ID, type (e.g., t2.micro, m5.large), region, and current operational status (running, stopped, terminated). It also shows the uptime percentage, total downtime, and a health timeline so you can see when the instance was up or down over the selected time period.
Time-series graphs are available for the following metrics:
| Metric | What It Shows |
| CPU Utilisation | Tracks processor usage over time. Sustained high CPU can indicate the instance is undersized or experiencing abnormal load. Consider upgrading the instance type if this persists. |
| Network In/Out | Monitors inbound and outbound data transfer rates. Unexpected spikes can indicate unusual traffic patterns or potential security concerns. |
| EBS Read/Write Bytes | Tracks the volume of data read from and written to attached EBS storage volumes. High values over time can point to disk-intensive workloads that may benefit from storage optimisation. |
| EBS Volume Read/Write Bytes | Provides a per-volume breakdown of disk I/O activity, useful when multiple volumes are attached to a single instance. |
Displays details of all EBS volumes attached to the EC2 instance, including volume type, size, and current status.
Automatically generates actionable recommendations to optimise the performance, security, and cost efficiency of your EC2 instances. For example, Insights may flag under-utilized instances that could be downsized to reduce costs, or highlight security group misconfigurations. These insights are updated daily based on real-time data.
| Symptom | Likely Cause | Fix |
| Instance showing as unavailable | The instance may be stopped or terminated in AWS | Check the Outages tab for downtime history and cross-reference with the AWS console |
| Metrics showing gaps | CloudWatch detailed monitoring is not enabled on the instance | Enable detailed monitoring in the AWS EC2 console (adds cost) |
| High CPU with no obvious cause | The instance may be undersized for its workload | Check Cloudmon Insights for auto-generated recommendations, including instance resize suggestions |
| Alarms not triggering as expected | Alarm thresholds may not be configured for this instance | Go to the Alarms tab on the instance detail page and add or review alarm rules |