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.