Every session and command runs as one OS account on the node. IAM decides who may
be which account. The agent creates ezgh-user itself; named accounts must already exist.
| Account | Created by | Sudo | Usable |
|---|---|---|---|
ezgh-user |
The agent, on first use | No, unless the project turns it on | Always |
Named accounts (root, deploy) |
You | As configured on the machine | Always |
Account names match ^[a-z_][a-z0-9_-]{0,31}$.
ezgh-user
ezgh-user is a node’s shared account, with no password and a home directory. It has no sudo
by default, so a policy that allows ezgh-user but not root really keeps people out of root.
The project setting ezgh-user sudo gives it passwordless sudo on the project’s nodes, from
its next session on each node.
Named accounts
A named account such as root or deploy must already exist on the machine; the agent never
creates one. A session or command for an account that doesn’t exist ends with
osUser_not_found.
Being allowed to be root, or ezgh-user with sudo, means being trusted with the whole machine:
such a person can change the agent and what it reports, and leave access behind that Fleets can’t
remove.
Acting as the node bot
Anyone with a shell on a node, in any account, can act as the node’s
node bot: on an EZGH instance, any process can fetch
the instance bot’s key from the metadata service. Give node bots FleetsManagedNodeAccess and
nothing else.