Show HN: Awsmux – Multi-account AWS CLI, up to 5.4x faster, 7.4x fewer tokens

AWS users are split as this speed tool promises fleet-wide control without the usual chaos

TLDR: Awsmux says it can run one cloud command across huge AWS setups much faster, while adding a human approval gate for risky actions. Commenters were less dazzled by the speed than by the bigger question: why are teams juggling so many separate accounts, and do they even need this tool if AWS already offers company-wide visibility?

A new Hacker News demo called Awsmux is pitching a very seductive fantasy: press one button, and your command races across hundreds of Amazon cloud accounts in seconds instead of forcing you to babysit endless slow loops. The creator claims it can be up to 5.4 times faster and use far fewer AI-generated words, with a built-in approval step that blocks dangerous changes unless a human signs off. In plain English: it’s trying to make massive cloud setups less of a slog and a lot less scary.

But the real popcorn moment was in the comments, where the community immediately turned this into a philosophical brawl about whether people should even have that many separate accounts in the first place. One of the strongest reactions came from a baffled reader basically asking, why is everyone living in a mansion with 100 locked rooms? That set the tone: some people saw Awsmux as a clever fix for a real pain, while others saw it as a shiny bandage for a problem companies created themselves.

Then came the classic power-user flex. Another commenter argued that if your AWS setup already has the company-wide tracking tools Amazon provides, you can often find what you need without marching through every account one by one. Translation: nice trick, but maybe the grown-ups already have another way. The vibe was equal parts impressed, skeptical, and lightly roasting—less “wow, amazing” and more “cool demo, but are we solving cloud chaos or just speedrunning it?”

Key Points

  • Awsmux runs AWS CLI commands across many accounts and regions in parallel, verifies identities first, and merges results into a single output stream.
  • For mutating operations, awsmux generates an immutable plan that must be approved before apply, with hash validation to detect tampering.
  • The article reports a 150-session benchmark in which awsmux was 1.3x to 2.9x cheaper, 2.3x to 5.4x faster, and produced up to 7.4x fewer output tokens than a raw-shell AWS CLI approach.
  • A bundled sandbox provisions a fictional 100-account fleet on a pinned LocalStack container using Go, Docker, and the aws CLI, with no real AWS credentials required.
  • For real AWS environments, awsmux uses existing AWS config and credentials files, supports SSO, static keys, and credential_process, and executes through the aws CLI with STS identity verification.

Hottest takes

“What’s the value of having a ton of silo’d accounts” — chaos_emergent
“You can build most of the graph from that alone” — thedougd
“without traversing accounts” — thedougd
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.