AWS Cloud Monitoring
CloudWatch data merged with your on-premises infrastructure
What it does
AlertMonitor pulls CloudWatch metrics and CloudTrail events into the same alert stream as your on-premises infrastructure. EC2 instances, VPCs, S3 buckets, and RDS databases appear alongside physical hardware in your network map. Security and performance events from AWS are normalized, AI-enriched, and actioned by your analyst team — no separate cloud monitoring console.
Hybrid visibility without an extra tool: Most SMBs run a hybrid infrastructure — some on-prem, something in AWS, maybe Azure too. Managing separate monitoring consoles for each creates blind spots at the seams. AlertMonitor merges all of it into one alert stream under one analyst team.
Capabilities
- EC2 instance health: CPU, memory, disk, network — with EBS volume performance
- CloudTrail security events: root account usage, IAM changes, security group modifications
- S3 bucket policy changes and public access configuration drift alerts
- RDS availability and performance metrics: CPU, connections, replica lag
- VPC flow log anomaly detection: unexpected inter-subnet traffic patterns
- AWS Cost anomaly alerts — unexpected spend spikes triggered by misconfigurations
- EC2, RDS, and Lambda appear in the unified network map alongside on-prem hardware
How it works
CloudWatch metrics are ingested via the AWS SDK using read-only IAM credentials (minimum required permissions documented in the AWS IAM guide). CloudTrail events are consumed from an S3 bucket or directly via CloudTrail API. All cloud data is normalized to the AlertMonitor event schema and processed through the same AI enrichment pipeline as on-premises events.