AWS Lambda viewer

mnml-aws-lambda is a terminal browser for AWS Lambda — list every function in a region (or watch a hand-picked set), inspect runtime / memory / timeout / handler, open the console, yank an ARN. Runs standalone in any terminal.

┌─ lambda ──────────────────────────────────────────────────────────────┐
│ ▸1.All (42)  2.Watched (5)                                            │
└───────────────────────────────────────────────────────────────────────┘
┌─ functions (42) ──────────┐ ┌─ detail ────────────────────────────────┐
│ ▸ api-handler   nodejs20.x│ │ Name          api-handler               │
│   ingest-worker python3.12│ │ Runtime       nodejs20.x                │
│   ses-bouncer   python3.11│ │ Handler       index.handler             │
│   thumb-gen     go1.x     │ │ Memory        512 MB                    │
│   …                       │ │ Timeout       30s                       │
│                           │ │ Code size     1.2 MB                    │
│                           │ │ Arch          arm64                     │
│                           │ │ Package       Zip                       │
│                           │ │ Modified      2026-06-02T12:34:56+0000  │
│                           │ │ Role          lambda-role               │
└───────────────────────────┘ └─────────────────────────────────────────┘
  1-9 tab · ↑↓/jk move · l tail logs · o console · y yank ARN · r refresh · q quit

Install

cargo install --git https://github.com/chris-mclennan/mnml-aws-lambda --tag v0.2.0 mnml-aws-lambda

You’ll also need the AWS CLI on your $PATH with credentials configured.

Setup

1. Verify the AWS CLI works. aws lambda list-functions must succeed.
2. Run once to scaffold the config: mnml-aws-lambda.
3. Edit ~/.config/mnml-aws-lambda.toml — add your tabs.
4. Re-run.

Auth shape

Pure shell-out to the aws CLI — same chain as the other AWS siblings (env vars → shared credentials → SSO → IAM role).

Config

# Optional top-level region:
# region = "us-east-1"

refresh_interval_secs = 60

[[tabs]]
name = "All"
kind = "all"

[[tabs]]
name = "Watched"
kind = "watched"
watched = [
  "api-handler",
  "ingest-worker",
]

Field	Required	Notes
name	yes	Tab strip label
kind	no	"all" (default) or "watched"
watched	when kind = "watched"	Explicit list of function names
region	no	Per-tab region override

Layout

• Tab strip: one tab per [[tabs]] entry, with per-tab function-count badge
• Functions table (left, 45%): name + runtime
• Detail panel (right, 55%): focused function’s full config (name / runtime / handler / memory / timeout / code size / arch / package / last-modified / role / ARN / description)
• Status: active count, key hints

Keys

Chord	Action
1-9	Switch to that tab
Tab / BackTab	Cycle tabs
↑ / k, ↓ / j	Move selection
PgUp / PgDn	Jump 10 rows
g / G	Top / bottom
Enter / o	Open Lambda console for the focused function
y	Yank focused function’s ARN to clipboard
l	Tail logs — spawns mnml-aws-cloudwatch-logs scoped to /aws/lambda/<focused-fn>
r	Refresh active tab
q / Esc / Ctrl+C	Quit

l — the cross-sibling log handoff

A Lambda function’s logs live in CloudWatch under /aws/lambda/<function-name>. Pressing l on a focused function spawns the mnml-aws-cloudwatch-logs sibling already scoped to that group:

mnml-aws-cloudwatch-logs \
  --log-group /aws/lambda/<focused-fn> \
  --log-group-name <focused-fn> \
  [--region <r>]

The launched viewer lands in a one-off single-tab session tailing exactly that log group — no need to switch tabs, no need to touch the CloudWatch viewer’s config. The status text on the Lambda viewer shortens to tailing /aws/lambda/<fn> while the sibling is running.

This is the first cross-sibling handoff in the family — Lambda’s data model points at CloudWatch’s, so they compose cleanly. The same pattern (parent sibling synthesising a one-off CloudWatch tab) is the planned hook for any future sibling whose resources emit CloudWatch logs.

Two run modes

Standalone

mnml-aws-lambda

Hosted as a mnml Pty pane

:term mnml-aws-lambda

Wire it into mnml’s left rail

mnml-aws-lambda ships as a default chip in mnml’s rail under INTEGRATIONS. Bound to <leader>i L in the whichkey leader menu (vim mode), or palette-runnable as forge.open_lambda.

Status

v0.2 — l now auto-scopes the launched mnml-aws-cloudwatch-logs sibling to /aws/lambda/<focused-fn> via the new --log-group / --log-group-name / --region CLI flags (added in CloudWatch viewer v0.2.0). The cross-sibling handoff is now real — the user lands directly in a one-off log tail for the focused function, without having to switch tabs in the launched viewer. Status text on the Lambda viewer shortens to tailing /aws/lambda/<fn>.

v0.1 — list (paginated) + watched filter, focused-function detail panel, console open, ARN yank, log-tail launch (sibling spawned bare; user had to switch tabs).

Held back for v0.3+:

• Invoke with test payload picker (i chord)
• Errors-24h tab kind (CloudWatch Metrics integration)
• Per-function env-var count + concurrent-execution stats
• Recent invocation list

Source

github.com/chris-mclennan/mnml-aws-lambda. MIT.