Why Filter Resources?
Some cloud resources are created and managed by other resources. For example:- EC2 instances in an Auto Scaling Group are managed by the ASG
- Node instances in an EKS Auto Mode cluster are managed by EKS
- Resources created by CloudFormation are managed by the stack
How Filtering Works
During discovery:- Your plugin’s
List()returns native IDs of resources - The agent calls
Read()on each resource to get its properties - Filters evaluate JSONPath expressions against those properties
- Resources matching a filter are skipped (not added to inventory)
Implementing Filters
Return filters from your plugin’sDiscoveryFilters() method:
eks:automode:.
Filter Logic
Within a filter: All conditions must match (AND). A resource is excluded only if every condition in the filter evaluates to true. Between filters: Any filter can exclude (OR). If you return multiple filters, a resource is excluded if it matches any one of them.Condition Structure
- PropertyPath: A JSONPath expression evaluated against the resource properties
- PropertyValue: If empty, the condition matches when the path returns any value. If non-empty, the condition matches when the path returns this exact string.

