See everything · Multi-Cloud Inventory

Every resource, every account, one search box.

CloudMonitor reads your AWS accounts, Azure subscriptions and Google Cloud projects through their read-only APIs and keeps one searchable inventory, refreshed every hour.

AWS Azure Google Cloud Included in every plan
01 What’s included

Multi-Cloud Inventory, in detail.

Every resource in AWS, Azure and GCP, one search. Here is exactly what CloudMonitor does — and where its coverage stops today.

13 AWS resource types

EC2, EBS, S3, Lambda, RDS, DynamoDB, Auto Scaling groups, ECS and EKS clusters, VPCs and subnets, security groups, ALB/NLB load balancers, Route 53 zones and IAM users.

Azure and Google Cloud too

Azure VMs with power state, managed disks, storage accounts, SQL, MySQL and PostgreSQL servers, App Service, AKS, Key Vault and Redis. GCP Compute Engine, disks, Cloud Storage, Cloud SQL and Cloud Functions.

Every enabled region

AWS accounts are swept across every region you have enabled, plus global services such as S3, IAM and Route 53. Azure subscriptions and GCP projects are read in full.

Search, filter, sort

Free-text search with filters for region, status and flags like idle, public or unencrypted, with server-side sorting and pagination for large estates.

Export the exact view

Download whatever you have filtered as CSV, ready for an audit, a CMDB update or a spreadsheet hand-off.

Refreshed every hour

Inventory syncs hourly on its own, and you can trigger a manual sync from the account page whenever you need a fresh picture.

02 How it works

Three steps, no agents to install.

1

Connect read-only access

An IAM key with ReadOnlyAccess for AWS, a Reader service principal for Azure, a Viewer service account for Google Cloud.

2

Let the first sweep run

CloudMonitor lists resources region by region and stores a snapshot of each one with its type, region, status and flags.

3

Search across everything

One search box and one set of filters for all of your clouds, with CSV export of any view.

Why a single cloud inventory matters

Most teams don’t lose track of their cloud because they are careless. They lose track because every provider has its own console, its own naming and its own idea of a “resource”. One team launches in eu-west-1, another in an Azure subscription nobody else can see, and a proof of concept lives on in a Google Cloud project long after the person who built it has moved on.

CloudMonitor fixes the visibility problem first, because every other question — what can we save?, what is exposed?, what is idle? — depends on knowing what exists.

What gets collected

On AWS, CloudMonitor reads thirteen resource types across every region enabled on the account, plus global services such as S3, IAM and Route 53. On Azure it reads virtual machines with their power state, managed disks and storage accounts, and picks databases, App Service, AKS, Key Vault, Redis and networking out of the subscription’s resource list. On Google Cloud it reads Compute Engine instances, persistent disks, Cloud Storage buckets, Cloud SQL and Cloud Functions.

Each resource is stored with its provider, type, region, status and the configuration flags that matter for cost and security: idle, public, unencrypted. That is what makes a query like “every public storage bucket, in any cloud” a single filter instead of three console sessions.

Built for large estates

Search, filtering and sorting happen on the server with pagination, so an inventory of tens of thousands of resources stays fast. If a full AWS sweep is slower than you would like, you can switch region scanning to active mode, which only revisits regions that already hold resources between full daily sweeps.

Read-only, by design

Inventory uses each provider’s standard read APIs and nothing else. CloudMonitor cannot create, change or delete a resource, and the credentials you connect are encrypted at rest with AES-256. Read more on the security page, or see how the same inventory feeds utilization patterns for your AWS fleet.

03 FAQ

Multi-Cloud Inventory
questions.

Something else? Talk to us — a person replies.

Which resource types does CloudMonitor inventory?

On AWS: EC2, EBS, S3, Lambda, RDS, DynamoDB, Auto Scaling groups, ECS and EKS clusters, VPCs and subnets, security groups, ALB/NLB load balancers, Route 53 hosted zones and IAM users. On Azure: virtual machines, managed disks, storage accounts, SQL databases, MySQL and PostgreSQL flexible servers, App Service, VNets, public IPs, load balancers, AKS, Key Vault and Redis. On Google Cloud: Compute Engine, persistent disks, Cloud Storage, Cloud SQL and Cloud Functions.

Does CloudMonitor scan every AWS region?

Yes. By default every region enabled on the account is swept on each inventory sync, and global services such as S3, IAM and Route 53 are read once. You can optionally narrow scanning to regions that hold resources to make syncs faster.

How often is the inventory refreshed?

Every hour automatically. You can also start a manual sync from the cloud account page, with a five-minute cooldown between manual runs.

Does inventory scanning add to my cloud bill?

No. Inventory uses the providers’ standard Describe and List read APIs, which are not billed per call on AWS. Paid APIs such as AWS Cost Explorer are called on a slower, separate schedule.

Turn on
the radar.

Create a workspace, connect your first account read-only and see what your clouds have been hiding.

FREE PLAN · NO CREDIT CARD · READ-ONLY ACCESS