---
title: "Monitor AWS, Azure, and GCP in one place | Grafana Labs"
description: "One view, one query language, and one alerting system across AWS, Azure, and GCP."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## Cloud Provider Observability

[Cloud Provider Observability](/docs/grafana-cloud/monitor-infrastructure/monitor-cloud-provider/) is a turnkey app for monitoring AWS, Azure, and Google Cloud. It’s built for organizations that have outgrown native CSP tooling.

Instead of:

- Separate native consoles, you get one app for all three clouds
- Different proprietary query languages, you have open standards (PromQL and LogQL)
- Separate alerting systems, there is one unified alerting engine

| Provider  | What you monitor                                                     |
|-----------|----------------------------------------------------------------------|
| **AWS**   | EC2, RDS, Lambda, S3, ELB, ECS, and more                             |
| **Azure** | VMs, Azure SQL, Functions, Storage, App Services                     |
| **GCP**   | Compute Engine, Cloud SQL, Cloud Functions, Google Kubernetes Engine |

[Try it out in Grafana Play](https://play.grafana.org/a/grafana-csp-app/aws)

## What keeps you up at night?

Role / WorriesWhat you get with the app

**Cloud Admin**

- Constantly switching between different cloud consoles to check what’s happening
- Each console has its own way of doing things

<!--THE END-->

- One place to manage and monitor all three clouds
- No more context switching between consoles

**SRE, DevOps Engineer**

- When something breaks, is the problem in AWS, Azure, or GCP?

<!--THE END-->

- Pre-built dashboards and alerts for each provider, all in one place
- Logs from all three clouds accessible in the same tool

**Developer**

- Is my app slow because of my code, or is something wrong with the cloud services underneath it?
- How do I figure this out without becoming an expert in each cloud’s tooling?

<!--THE END-->

- Pre-built views of cloud services that don’t require deep knowledge of each provider’s tooling

**Engineering Manager, VP Engineering**

- Cloud bills growing faster than the team can explain
- Paying a premium on top of that for observability tools

<!--THE END-->

- Priced on metrics ingested, so no per-host premium. With growth, you pay for the telemetry you generate, not a flat charge per resource on top of it.