Search Syntax

You can use one or more of the following search syntaxes with the Boolean search operators to create complex search queries.

Search Syntax

Tokens	Description	Cloud Platform
name:	add resources with this name.	All
region:	add everything in a region.	All
source:	add everything in the specified source.	All
type:	add a specific resource type.	All
subnet:	add everything in the Subnet matching this ID.	All
id:	add everything with this id: token	All
ip:	add everything that matches or includes an IP.	All
Any other value followed by ' : ' (Tags)	add everything from specified tag.	All
resource_group:	add everything in the Resource Group matching this ID.	Azure
virtual_network:	add everything in the Virtual Network matching this ID.	Azure
vpc:	add everything in the VPC matching this ID.	AWS & Google Cloud
project:	add everything in this Project.	Google Cloud

Search Operators

The search syntax also provides a set of modifiers and operators allowing you to combine the tokens into complex queries to match resources across all providers, allowing you to define exactly what should be on the diagram.

Operators	Description
AND	Allows you to join queries together to limit or expand the results returned. Example: type:"AWS::EC2::Instance" and vpc:vpc-1234 will search for all resources that are EC2 Instances AND are within the VPC vpc-1234
OR	Allows you to join queries together to limit or expand the results returned. Example: region:us-west-1 or region:us-west-2 will return resources within us-west-1 OR within us-west-2
- (minus)	By adding a minus ( - ) before your search token you can remove any resources that match a query. Example: vpc:vpc-1234 and -name:dev-* will return resources that are in the VPC vpc-1234 and don’t have a name starting with dev-
( brackets )	Grouping queries with brackets, a set of tokens together to create more complex queries by surrounding them with brackets. Example: vpc:vpc-1234 and (CostCenter:dev or CostCenter:test) will return all resources within the VPC vpc-1234 that have the tag CostCenter with a value of either dev or test.
@	Doing a Deep Search using @ sometimes you not only want to see the matched resources but anything connected to them as well. Example: @type:"AWS::EC2::Instance" will return all instances, as well as connected resources such as load balancers and ECS clusters.
*	Wildcard