Skip to main content
Upmetr automatically discovers and inventories cloud resources across all connected providers. The Resources page gives you a unified view of every resource in your infrastructure — compute instances, databases, DNS zones, storage buckets, serverless functions, and more — regardless of which cloud they live in.

​
Resource Discovery

When you add a cloud account, Upmetr immediately scans it for supported resource types. After the initial scan, discovery runs automatically every 15 minutes to keep your inventory up to date. Each discovered resource includes:
  • Name and ID — The resource’s name and provider-specific identifier
  • Type — The resource category (e.g., EC2 Instance, Cloud SQL, Droplet)
  • Status — Current state (Running, Stopped, etc.)
  • Region — The cloud region where the resource is deployed
  • Cloud Account — Which connected account owns the resource
Resource discovery requires the cloud_resources module. If your plan does not include this module, the Resources page will show an upgrade prompt.

​
Supported Resource Types

Upmetr discovers 27 resource types across four cloud providers:

​
AWS

​
Google Cloud

​
Azure

​
DigitalOcean

​
Viewing Resources

Navigate to Resources in the sidebar to see your full cloud inventory. The page displays:
  • Summary cards at the top showing total resource count, EC2 instances, RDS databases, and running resources
  • Filter bar with six filters that can be combined
  • Paginated table listing all matching resources

​
Available Filters

Select a Provider first to narrow the Type dropdown to only the resource types available for that provider.
Use the Refresh button in the filter bar to reload the current view without changing your filters. To remove all filters at once, click Clear all.

​
Resource Statuses

​
Compute Management

Upmetr allows you to start, stop, and reboot EC2 instances directly from the dashboard.
Compute management actions are restricted to Superadmin users and require the compute_management module on your plan. These actions affect live infrastructure — use with caution.

​
Available Actions

​
How It Works

  1. Navigate to a resource detail page for an EC2 instance
  2. Click the desired action button (Start, Stop, or Reboot)
  3. A confirmation modal appears — you must explicitly confirm the action
  4. Upmetr executes the action via the AWS API and updates the resource status
  5. The action is recorded in the Audit Log for security tracking
Compute management currently supports AWS EC2 instances only. Your IAM policy must include ec2:StartInstances, ec2:StopInstances, and ec2:RebootInstances permissions. See the Cloud Accounts guide for IAM policy details.

​
Manual Discovery

If you need to refresh your resource inventory immediately (for example, after launching new instances), you can trigger a manual discovery:
  1. Go to Settings > Cloud Accounts
  2. Click the Discover button on the account you want to re-scan
  3. Upmetr scans the account and updates the resource list
The next automatic discovery will continue on its regular 15-minute schedule.

​
Troubleshooting

  • Ensure you clicked Discover on the cloud account after adding it, or wait up to 15 minutes for automatic discovery
  • Verify that the credentials have the correct read permissions for the resource types you expect (e.g., ec2:Describe*, rds:Describe* for AWS)
  • Check Settings > Cloud Accounts and run Test Connection to confirm the account is connected
  • Resources are refreshed every 15 minutes automatically
  • Click the Refresh button on the Resources page to reload the current data from the database
  • To force a full re-scan from the cloud provider, go to Settings > Cloud Accounts and click Discover
  • Verify the IAM policy or service account role includes permissions for the missing resource type
  • Some resource types are region-specific — make sure the account’s default region or multi-region scanning covers the expected regions
  • Check that the resource exists and is not in a terminated state in your cloud provider’s console
  • Compute management requires the compute_management module — check your plan includes it under Settings > Billing
  • Only Superadmin users can perform start/stop/reboot actions
  • The IAM policy must include ec2:StartInstances, ec2:StopInstances, and ec2:RebootInstances in addition to read-only permissions