Tools

EdgeCommons tools are command-line programs you run from your own shell — to operate, inspect, or develop against a running system. They are built on the same edgecommons library as the components, so what a tool writes is exactly what a component reads, but a tool is not deployed to an edge device.

For the deployable pieces of an edge solution — adapters, processors, sinks, bridges, services, and consoles — see Components.

Tool	Language	What it does
ec-uns-cmd	RUST	EdgeCommons UNS command-line tool. Sends a cmd/sb/* (or any) command to a component’s command inbox over the UNS and prints the correlated reply; reaches Greengrass/IPC components via uns-bridge. Operate and test any EdgeCommons component from the shell.
ec-secrets	RUST	EdgeCommons vault-seeding CLI. Populates and manages the LOCAL credentials vault (set/get/list/delete/import) that components read via gg.credentials() and $secret refs — same envelope encryption + KeyProvider (file/env/kms). Built on the library, so what it writes is exactly what a component decrypts.
edgecommons	RUST	The EdgeCommons CLI. One static binary that scaffolds components in four languages, validates their config and artifacts against the canonical schema, moves them between library versions, packages and releases them, and compiles a deployment definition into platform-native artifacts. Carries the templates and schema inside itself, so it works offline.