Guide / Search

Search

/ opens the search bar. What you type does two things at once: an @prefix switches service, and the rest fuzzy-matches against every indexed field of the resources in view.

@ec2                 switch to EC2
@ec2 web             switch to EC2 and fuzzy-search "web"
ec2:web              colon syntax, same thing
@all payments        search every warm cache entry, across services
tag:env=prod         exact tag filter (composes: tag:env=prod api)
arn:aws:iam::…       paste an ARN — it fuzzy-matches rather than erroring

Typing @e pops a completion dropdown; Tab completes to the first match. Enter closes the bar and keeps the filter applied; Esc clears it.

What is indexed

Matching is fuzzy with a score threshold, over ids, names, IPs, CIDRs, availability zones, tags, ARNs, usernames, emails, and per-service extras such as every secondary private IP on a network interface or every resource id in a GuardDuty finding. A pasted ARN or instance id lands on the exact resource.

Tag filters

tag:key=value terms are exact, case-insensitive tag filters that compose with the fuzzy part: tag:env=prod api shows resources tagged env=prod whose fields match api. tag:key alone matches any value.

@all

@all <text> searches everything already cached this session, across services, and shows a service badge on every row. It never fires a fetch, and it says how many services it covered, so visit the services you care about first. Enter on a result jumps to it in its own service.

  • F cycles a state filter over the states present in the current view (running, stopped, failed…).
  • a hides rows the service considers noise: default VPCs, automated snapshots, passed checks. Noise shows by default; a opts in to hiding it.
  • z cycles the sort: load order, name ascending, name descending, state.