1. Home
  2. Products
  3. ebman

ebman Available

A k9s-style terminal UI for AWS Elastic Beanstalk.

Triage red environments, stream logs, diff and edit config, run SSM sessions and ship new versions — all from the keyboard. If you’ve used k9s, the muscle memory carries: : for commands, / to filter, Enter to drill in, ? for help.

$ brew install tombaldwin/tap/ebman

View on GitHub · open source, MIT / Apache-2.0

Filter to a red env, :why for a one-screen diagnosis, drill into instances, open an embedded SSM session — without leaving the terminal.

From red to fixed in five keystrokes

Production goes red at 3am. From your terminal:

  1. ebman — launch; prod-api shows up tinted red in the table.
  2. /prod-api ↵ — jump straight to it.
  3. :why — recent events, alarms, instance health and last deploys, all in one overlay.
  4. :diff prod-api staging-api — confirm staging is still on the previous version.
  5. :rollback — redeploy the last-known-good version label, with a five-second undo window.

Every action and its outcome lands in ~/.cache/ebman/audit.log. The AWS-console alternative is a minimum of five page-loads, two tabs, and zero audit trail.

What’s inside

  • Live environment table Sort, filter, group by app, health sparklines and severity tints across every env — with mouse support.
  • One-screen triage :why gathers recent events, alarms, instance health and last deploys into a single overlay, with a DLQ peek for worker envs.
  • Honest health Alarms in ALARM, DLQs with a backlog and stale platforms surface on the row itself — not three tabs deep.
  • Forensics :diff option-setting deltas between envs, :lineage for the deploy timeline, :alarm-history for CloudWatch state changes.
  • Daily-driver writes Env vars, tags, deploys (label, local zip or S3, with --preview), saved configs, alarms and capacity — behind typed-name confirms.
  • Multi-account & scriptable Parallel queries across regions and AssumeRole accounts, plus --read-only, a full audit log and a headless ebman ctl / --json interface for CI.

Why ebman?

You probably already use one of these — here’s where each falls short for daily Elastic Beanstalk triage:

ToolGood atWhere it falls short
AWS ConsoleApproachable, complete UI.Page loads, eventually-consistent state, five tabs to triage one env. Painful at 3am.
eb CLIA single project’s deploy flow.No multi-env view, no live drill-down, no diff between envs, no DLQ workflow.
aws elasticbeanstalkRaw, scriptable API access.You build the workflow out of --query / jq pipelines yourself.
k9s + EKSThe pattern ebman is modelled on.Doesn’t exist for Elastic Beanstalk.

ebman is k9s-for-EB: keyboard-driven, drill-down-first, one screen for ‘what’s wrong’ and ‘what changed’ — built for operators who triage red envs daily and don’t want the console round-trip.

Install

Homebrew (macOS / Linux):

$ brew install tombaldwin/tap/ebman

Cargo:

$ cargo install ebman

Or download a pre-built binary:

macOS · Apple Silicon macOS · Intel Linux · x86_64

v0.22.0 · all builds & checksums · uses the standard AWS credential chain (AWS_PROFILE / ~/.aws/credentials, instance role)

GitHub · crates.io · open source, MIT / Apache-2.0

Have a big idea to build, a problem to solve, or a system that’s overdue an upgrade?

Get in touch