HN Reader

I couldn't get this to run successfully.

More broadly, I have concerns about introducing a middleware layer over AWS infrastructure. A misinterpreted command or bug could lead to serious consequences. The risk feels different from something like k9s, since AWS resources frequently include stateful databases, production workloads, and infrastructure that's far more difficult to restore.

I appreciate the effort that went into this project and can see the appeal of a better CLI experience. But personally, I'd be hesitant to use this even for read-only operations. The direct AWS cli/console at least eliminates a potential failure point.

Curious if others have thoughts on the risk/benefit tradeoff here.

Only tangentially related, but: what is the appeal of TUI's? I don't really understand.

The advantages of CLI's are (IMO) that they compose well and can be used in scripts. With TUI's, it seems that you just get a very low fidelity version of a browser UI?

Should have a Price Of Current Changes menu bar item! So you can see if your changes cost $.01 or $10,001.

Somehow every 15 line shell script I write now turns into a 50kloc bun cli or tui app. Apparently there are many such cases.

I thought the title meant the AWS UI was “terminal”, which I would be on board with

Looks great! If you have multiple AWS accounts in your org, you probably want to use something like aws-sso-util to populate your profiles so you can quickly swap between them

Crashes on first use. Not a good way to go viral.

How much of this was made with LLM?

I run a neocloud and our entire UX is TUI-based, somewhat like this but obviously simpler. The customer feedback has been extremely positive, and it's great to see projects like this.

ssh admin.hotaisle.app

Please don't use or suggest using homebrew as a Linux installation solution. It's better to simply point at the binaries directly.

Nice! A while back I had started something similar for Azure but it never really got traction (or nearly as polished as this!). It's a rough proof of concept but maybe it'll be useful to Azure users:

https://github.com/brendank310/aztui

> // TODO: Handle credential_source, role_arn, source_profile, sso_*, etc.

So it does not support any meaningful multi-account login (SSO, org role assumption, etc), and requires AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY. That's a no-no from security POV for anything in production, so not sure what's the meaningful way to use that.

Great TUI app. Kudos & Ellerinize saglik

Interesting, looks like k9s... but for AWS

Embarrassingly dumb question: if you’re one of the few users who don’t run a dark background terminal … how well do these TUI render (in a light background)?

I wish more TUI designers would spend some time playing with Hercules and experiencing the old "mainframe" way of arranging interfaces. Those guys really knew what they were doing.

Is there a Rust port or binding for ncurses?

wow, that looks like k9s for aws. That's awesome

Nice idea but I won't trust a tool that first the commit is 11 hours ago.

looks good. definitely will try

Very cool

Looks very nice! Need to test if it supports AWS_ENDPOINT_URL so it works with LocalStack.

claude code can do this, natively without a custom implementation

yea let me just give access to my company AWS account credentials to this program made by some random dude on the internet

This guy stole this idea and basically the whole code base from another developer and ran it through an LLM to recreate it.