Filtering and Tag Search
With thousands of resources across multiple cloud providers, finding the right resource quickly is essential. CloudYali's Asset Inventory includes an advanced filtering system with provider-scoped rules and tag-based search operators that let you narrow down to exactly what you need.
Opening the Filter Panel
Click the Filters button in the inventory toolbar to open the filter panel. A badge on the button shows the count of active filters. Click Clear next to it to reset all filters at once.
How Filter Rules Work
Filters are organized as rules with conditions:
- Each rule is scoped to a single cloud provider (AWS, GCP, Azure, Fastly, or Anthropic)
- Within a rule, all conditions are combined with AND logic — every condition must match
- Multiple rules are combined with OR logic — any rule can match
Example: "Show me all AWS EC2 instances in us-east-1 OR all Azure VMs in West Europe"
| Rule | Provider | Conditions |
|---|---|---|
| Rule 1 | AWS | Resource Type = EC2::Instance AND Region = us-east-1 |
| Rule 2 | Azure | Resource Type = Microsoft.Compute/virtualMachines AND Region = westeurope |
Creating a Filter Rule
- Click Filters in the toolbar to open the filter panel
- Select a cloud provider from the provider dropdown
- Click Add Condition to add filter criteria
- Choose a field, operator, and value
- Add more conditions as needed (AND logic within the rule)
- Click Apply to execute the filter
To add another rule (OR logic), click Add Rule and repeat the process.
Available Filter Fields
| Field | Description | Label Varies by Provider |
|---|---|---|
| Account | The account/project/subscription the resource belongs to | "Account" (AWS, Fastly, Anthropic), "Project" (GCP), "Subscription" (Azure) |
| Region | Cloud region or location where the resource is deployed | Same across all providers |
| Resource Type | The specific resource type identifier | Provider-prefixed (e.g., EC2::Instance, compute.googleapis.com/Instance) |
| State | Whether the resource is currently active or has been deleted | Active or Deleted |
| Tag | Resource tags or labels with advanced operators | Same across all providers (where tags are supported) |
The Account field label automatically changes based on the selected provider to match each cloud's terminology. For GCP, it shows "Project"; for Azure, it shows "Subscription".
Tag Filter Operators
Tag-based filtering supports six operators for precise resource discovery:
| Operator | Description | Use Case |
|---|---|---|
| Equal | Tag key has one of the specified values | Find all production resources: Environment = production |
| Not Equal | Tag key does NOT have the specified values | Exclude dev resources: Environment != development |
| Exists | Tag key is present on the resource (any value) | Find tagged resources: CostCenter exists |
| Not Exists | Tag key is NOT present on the resource | Find untagged resources: CostCenter does not exist |
| Empty | Tag key exists but has an empty value | Find resources with blank owner: Owner is empty |
| Not Empty | Tag key exists and has a non-empty value | Find resources with an assigned owner: Owner is not empty |
Tag Search Use Cases
| Goal | Operator | Tag Key | Value |
|---|---|---|---|
| Find untagged resources | Not Exists | CostCenter | — |
| Find resources by team | Equal | Team | platform-engineering |
| Find resources with blank owner | Empty | Owner | — |
| Exclude test environments | Not Equal | Environment | dev, test |
| Find all tagged resources | Exists | Environment | — |
| Find resources with assigned owner | Not Empty | Owner | — |
Tag-based filtering works for AWS (tags), GCP (labels), and Azure (tags). Fastly and Anthropic resources do not support tags, so tag filters will not match any Fastly or Anthropic resources.
Combining Filters
AND Logic (Within a Rule)
All conditions within a single rule must match. For example:
Provider: AWS AND Region: us-east-1 AND State: Active AND Tag
Environment= production
This returns only AWS resources in us-east-1 that are active AND tagged with Environment=production.
OR Logic (Across Rules)
When you add multiple rules, any rule matching is sufficient:
Rule 1: AWS + us-east-1 OR Rule 2: GCP + us-central1
This returns AWS resources in us-east-1 AND GCP resources in us-central1.
Persistent Filters
Your filter state is automatically saved in your browser's local storage. When you return to the Asset Inventory page, your last-used filters are restored automatically. Use the Clear button in the toolbar to reset all filters and start fresh.
Related Documentation
- Unified Asset Inventory Overview — Main inventory documentation
- Cloud Tag Governance — Define and enforce tag standards across your cloud resources
- Configuration Change History — Track changes to the resources you find
- Resource Cost Integration — View costs for filtered resources