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

macOS · Apple Silicon macOS · Intel Linux · x86_64

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

ebman's environment table: a sortable, filterable list of Elastic Beanstalk environments showing status, health, instance count, platform, version, CNAME, cost and age.

The live environment table — status, health, versions and cost across the whole fleet, sortable and filterable. Drill into any env, or hit :why on a red one.

From red to fixed in five keystrokes

Production goes red at 3am. From your terminal:

ebman — launch; prod-api shows up tinted red in the table.
/prod-api ↵ — jump straight to it.
:why — recent events, alarms, instance health and last deploys, all in one overlay.
:diff prod-api staging-api — confirm staging is still on the previous version.
: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.

ebman's :why overlay diagnosing a red environment: cost, recent events, alarms, instance health and recent deploys, all on one screen.

:why on a red env: recent events, alarms, instance health and the last few deploys — one screen, no console tabs.

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.
Health up front 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.

ebman drilled into an environment on the Instances tab: per-instance health (Severe / Ok), instance type and availability zone, with tabs for Health, Events, Metrics, Logs and Config.

Drill into any env — here the Instances tab, with per-instance health, type and AZ. Tabs for Health, Events, Metrics, Logs and Config, plus :ssh for an embedded SSM session.

Why ebman?

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

Tool	Good at	Where it falls short
AWS Console	Approachable, complete UI.	Page loads, eventually-consistent state, five tabs to triage one env. Painful at 3am.
`eb` CLI	A single project’s deploy flow.	No multi-env view, no live drill-down, no diff between envs, no DLQ workflow.
`aws elasticbeanstalk`	Raw, scriptable API access.	You build the workflow out of `--query` / `jq` pipelines yourself.
k9s + EKS	The 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 grab a pre-built binary — macOS (Apple Silicon / Intel) and Linux x86_64, with checksums, from the Releases page (the download buttons at the top point at the latest). ebman uses the standard AWS credential chain (AWS_PROFILE / ~/.aws/credentials, instance role).

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