# Cloud & Infrastructure Monitoring

Cloud and infrastructure services form the backbone of your digital operations—and are often prime targets for security incidents. Sprinto monitors key performance and security parameters across AWS, Azure, GCP, and Oracle Cloud to ensure availability, performance, and compliance.

This article explains what infrastructure metrics are monitored, how Sprinto detects issues, and how you can resolve failing monitors across platforms.

***

### What is Monitored

Sprinto continuously tracks the following infrastructure components and metrics:

* CPU and memory utilisation
* Database latency and write capacity
* Load balancer health and latency
* Storage usage and connection limits
* Cloud-native alerting services (e.g., CloudWatch, Azure Monitor)

These monitors help identify resource exhaustion, service misconfiguration, or operational drift.

***

### Supported Platforms

1. **AWS**
2. **Azure**
3. **Google Cloud Platform (GCP)**
4. **Oracle Cloud Infrastructure (OCI)**

Each platform is integrated using official APIs and dashboards to automatically fetch metric status.

***

### Monitored Checks by Platform

#### 1. **AWS**

* **EC2**: CPU utilisation
* **EBS**: Health status
* **ECS**: CPU and memory metrics
* **DynamoDB**:
  * Write capacity
  * Latency
* **SQS**: Visible messages (monitored via CloudWatch alarms)
* **ALB/CLB**: Latency and error response monitoring

#### 2. **Azure**

* **SQL Database**:
  * CPU utilisation
  * Encryption enforcement
* **Storage Accounts**:
  * Secure transfer settings
  * Network rules (default deny)
* **NSG**: Flow log configuration
* **Web Apps**: TLS version enforcement

#### 3. **Google Cloud Platform**

* **Cloud SQL**:
  * Memory utilisation
* **VPC**:
  * Flow log configuration

#### 4. **Oracle Cloud**

* **Load Balancer**:
  * Active connection count
* **VCN**:
  * Flow log configuration

***

### Example Monitors

<table><thead><tr><th width="443.42578125">Monitor Description</th><th>Platform</th><th>Resolution Type</th></tr></thead><tbody><tr><td>CPU utilisation should be monitored on EC2</td><td>AWS</td><td>Auto / Evidence</td></tr><tr><td>NSG Flow logs should be enabled</td><td>Azure</td><td>Auto</td></tr><tr><td>GCP Cloud SQL memory usage should be monitored</td><td>GCP</td><td>Evidence</td></tr><tr><td>SQS visible messages alarm should be configured via CloudWatch</td><td>AWS</td><td>Evidence</td></tr><tr><td>Active connection count should be monitored on Load Balancer</td><td>Oracle Cloud</td><td>Evidence</td></tr></tbody></table>

***

### Resolving the Monitor in Sprinto

* For **automated monitors**, Sprinto will update the status during the next sync
* For **manual monitors**, you must:
  * Upload screenshots of configured alarms or monitoring dashboards
  * Attach policy or configuration exports where required
* Click **Mark as Resolved** once action is completed

***

### Best Practices

* Enable platform-native monitoring (e.g., CloudWatch, Azure Monitor)
* Define alarms for high CPU, memory, and error thresholds
* Use tagging and naming conventions for traceability
* Include critical metrics in your incident alerting workflows