Give Hermes Agent its own EC2 night shift

Goal: Run Hermes overnight without leaving my MacBook open.
Setup: agents used in source: Hermes Agent; tools/MCPs stated: AWS EC2, Terraform, AWS SSM, Tailscale, systemd, Telegram, EventBridge Scheduler.
Steps:
1. Provision an Ubuntu 24.04 EC2 box with Terraform: encrypted gp3, IMDSv2, termination protection, 0 inbound rules.
2. Manage it with AWS SSM; use Tailscale for private shell access.
3. Run Hermes as its own Linux user with a systemd user service; loginctl enable-linger hermes keeps it alive.
4. Auth headless: hermes auth add openai-codex --no-browser; smoke test: hermes -z "Reply with exactly: HERMES OK".
5. Telegram is the control plane (BotFather bot restricted to your user ID).
6. EventBridge starts EC2 at 11 PM and stops it at 7 AM.
Rules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.
Based on: Arc — https://x.com/c199benzene/status/2103986129452384726

Steps are from the source. Includes a “Based on” credit line.