Collector Kinds
Endpoint
Runs as a service on the machine you want inventoried. It inspects that machine directly: its processes, its container runtime, its GPUs, and the ports it listens on. It reads the binary name straight from the process, so it gives the most detailed local evidence. Use it for laptop fleets and single servers. Roll it out through your configuration management tool. Endpoint Collectors are available for macOS, Linux, and Windows.Network Scanner
Runs as a Docker container on a virtual machine inside the network. It finds services by probing the hosts it can route to. It records every host it cannot route to as a blind spot. Use it for detecting the AI services in private-network.In-Cluster
Installs as a Helm release into a Kubernetes cluster you already run. The Collector reads Services, Endpoints, and Pods through the in-cluster API, so you can skip provisioning a virtual machine.Cloud API
Calls the cloud provider APIs directly to list managed AI: Bedrock models and agents, SageMaker endpoints, AgentCore runtimes and gateways, and attached Guardrails. It runs as a Helm CronJob and authenticates through the cluster’s IAM integration. It needs an EKS cluster with an OIDC provider, plus an IAM role that trusts it.How Collectors Join a Target
A Collector proves it belongs to a Target with one of two credentials. Pick the one that matches how you install.
You can revoke both at any time. Revoking takes effect immediately. See Install a Collector for the steps.
Next
Install a Collector
Credentials, prerequisites, and the install steps for each kind.