Fleets gives you a shell on your machines from the console or the ezgh CLI, and runs commands
and saved scripts on one machine or a whole fleet. A small agent on each machine connects out to
EZGH as a bot, so there are no SSH keys to hand out, no inbound ports to open and no
bastions. IAM decides who may open a shell on which machine as which OS account, and every
session and command, and how each one ended, is recorded in Trails.
The agent runs on EZGH Compute instances and on any other Linux machine.
Install the agent
Create a node bot and register an instance or any other Linux machine.
Connect to a node
Open a shell from the console or with ezgh fleets shell.
OS accounts
ezgh-user and named accounts such as root.
Run commands and scripts
Run a command or a saved script on nodes by name or tag, with concurrency and error limits.
IAM
Policies, resource names and examples of who may be whom.
Trails events
What Fleets records for sessions, runs and nodes.
Concepts
| Term | Meaning |
|---|---|
| Node | A machine running the agent, registered in one project. A node on an EZGH instance is linked to it and has the instance’s tags. Resource type nod. |
| Session | One live shell on one node as one OS account. It ends when its terminal tab or ezgh fleets shell closes; Trails records who started it and how it ended. Resource type ssn. |
| Command run | One request to run a command or a script on a set of nodes, with concurrency and error limits. Resource type cmd. |
| Invocation | One node’s part of a command run: its status and exit code. |
| Script | A named script with versions, each with its own body and typed parameters. Resource type scr. |
| Node bot | The bot a node’s agent acts as. See Install the agent. |
What’s kept
Fleets keeps no output. Nothing a shell or a command prints or reads is stored, logged or sent back: each node in a run reports a status and an exit code. Sessions are listed only while they’re live; command runs are listed for 30 days after they end. Trails keeps the events, including each session’s account, who started it and how it ended, for its own retention.
Requirements
- Linux on amd64 or arm64, with systemd.
- Outbound HTTPS (port 443) to
fleets-api.ezghcloud.com,fleets-gateway.ezghcloud.comandorgs.ezghcloud.com, and toget.ezghcloud.com(path/fleets/) to install and update the agent. The agent listens on no port.
Pricing
Fleets is free.