Resource Inventory: See Every Cloud Resource Across AWS, Azure & GCP

import { Steps } from ‘@astrojs/starlight/components’;

Resource Inventory

Xplorr automatically discovers and tracks every cloud resource across your connected AWS, Azure, and GCP accounts. The inventory syncs alongside your billing data, so you always have a current view of what’s running and where.

Why It Matters

Your cloud bill is a sum of resources. If you can’t see the resources, you can’t control the cost. Common problems the inventory solves:

• Forgotten resources — A staging database nobody uses, still running at $180/month.
• Orphaned volumes — EBS volumes detached from terminated instances, costing $0.10/GB/month each.
• Region sprawl — Resources scattered across regions you didn’t intend to use.
• Tag gaps — Resources missing required tags, making cost allocation impossible.

What Gets Tracked

AWS

EC2 instances, EBS volumes, VPCs, subnets, security groups, NAT gateways, internet gateways, load balancers, RDS instances, RDS clusters, Lambda functions, DynamoDB tables, ElastiCache clusters, and S3 buckets.

Azure

All ARM resource types via the Resource Management API — virtual machines, disks, SQL databases, AKS clusters, Cosmos DB accounts, and more.

GCP

30+ resource types via the Cloud Asset API — Compute Engine instances, Cloud SQL, GKE clusters, BigQuery datasets, Cloud Storage buckets, and Cloud Run services.

How Data Is Collected

Resource inventory is collected during every cost sync. When Xplorr syncs billing data from your cloud accounts, it also queries resource APIs to discover current resources:

1. AWS — Uses EC2 DescribeInstances, RDS DescribeDBInstances, EBS DescribeVolumes, etc.
2. Azure — Uses the ARM Resource Management API to list all resources in the subscription.
3. GCP — Uses the Cloud Asset API to list resources across projects.

Each resource is upserted by its unique (cloud_account_id, resource_id) pair. New resources get a discovered_at timestamp. Existing resources get their metadata updated.

Browsing Inventory

Navigate to Inventory in the left sidebar of your console.

Filtering

Use the filter bar at the top to narrow results:

Filter	Options
Provider	AWS, Azure, GCP
Account	Any connected cloud account
Region	All regions discovered in your accounts
Resource type	EC2 Instance, EBS Volume, RDS Instance, etc.
Status	Running, Stopped, Available, etc.
Search	Free-text search across resource name and ID

The Filters dropdown auto-populates with distinct values from your actual resources, so you only see options that exist in your infrastructure.

Pagination

Results are paginated (up to 100 per page). Use the page controls at the bottom to navigate.

Access Control

• Admins see all resources across all accounts.
• Members and Viewers only see resources from accounts they’ve been granted access to via the team management settings.

Exporting to CSV

Click Export CSV to download up to 50,000 resources. The export includes:

Column	Description
Account	Cloud account name
Provider	aws, azure, or gcp
Resource Type	E.g., EC2 Instance, RDS Instance
Name	Resource name or identifier
ID	Cloud-native resource ID (e.g., i-0a3f...)
Region	E.g., us-east-1, westus2, us-central1
Status	Running, Stopped, Available, etc.
Tags	JSON object of all tags
Discovered At	When Xplorr first saw this resource
Updated At	Last time metadata was refreshed

Connecting to Recommendations

The inventory powers several recommendation types:

• Idle resources — EC2 instances, RDS databases, and EBS volumes with low utilization are flagged.
• Orphaned volumes — EBS volumes in “Available” status (not attached to any instance).
• Rightsizing — Over-provisioned instances identified by comparing resource metadata with cost data.

When you see a recommendation in the Recommendations page, you can cross-reference it with the inventory to see the full resource details.

Connecting to Tagging Policies

The inventory is the data source for tagging policy enforcement. When you define required tags, Xplorr checks every resource in the inventory for compliance. Resources missing required tags appear as violations.

API Access

Query the inventory programmatically:

# List resources with filters
curl -H "Authorization: Bearer $TOKEN" \
  "https://api.xplorr.io/api/v1/inventory?provider=aws&type=EC2%20Instance&status=Running&limit=50"

# Get filter options
curl -H "Authorization: Bearer $TOKEN" \
  "https://api.xplorr.io/api/v1/inventory/filters"

# Export as CSV
curl -H "Authorization: Bearer $TOKEN" \
  "https://api.xplorr.io/api/v1/inventory/export" -o inventory.csv

Tips

• Check inventory after every sync to spot newly launched resources before they accumulate cost.
• Filter by status “Stopped” to find resources you’re still paying storage costs on (EBS volumes attached to stopped instances).
• Use the search bar to quickly find a specific resource by name or ID when investigating an anomaly.
• Combine with tagging policies to enforce governance — if a resource shows up untagged, you’ll know about it immediately.