[HN Gopher] Show HN: Terminal UI for AWS
       ___________________________________________________________________
        
       Show HN: Terminal UI for AWS
        
       Author : huseyinbabal
       Score  : 118 points
       Date   : 2026-01-04 20:17 UTC (2 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | sylens wrote:
       | 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
        
       | latchkey wrote:
       | 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
        
         | Imustaskforhelp wrote:
         | Oh this looks really interesting as well.
         | 
         | Can you tell me more about what do you mean by Neocloud and
         | where are you exactly hosting the servers (do you colocate or
         | do you resell dedicated servers or do you use the major cloud
         | providers)
         | 
         | this is my first time hearing the term neocloud, seems like its
         | focused on AI but I am gonna be honest that is a con in my book
         | and not a pro (I like hetzner and compute oriented compute
         | cloud providers)
         | 
         | Share to me more about neoclouds please and tell me more about
         | it and if perhaps it could be expanded beyond the AI use case
         | which is what I am seeing when I searched the term neocloud
        
           | solumunus wrote:
           | > seems like its focused on AI but I am gonna be honest that
           | is a con in my book and not a pro
           | 
           | A service you have no use for or interest in is "a con in
           | your book", what?
        
           | latchkey wrote:
           | Neocloud has come to refer to a new class of GPU-focused
           | cloud providers. Sure, most of our customers use us for AI
           | purposes, but it is really open to anything GPU related.
           | 
           | We buy, deploy and manage our own hardware. On top of that,
           | we've built our own automation for provisioning. For example,
           | K8S assumes that an OS is installed, we're operating at a
           | layer below that which enables to machine to boot and be
           | configured on-demand. This also includes DCIM and networking
           | automation.
           | 
           | We colocate in a datacenter (Switch).
        
       | dionian wrote:
       | excellent
        
       | tvbusy wrote:
       | Nice idea but I won't trust a tool that first the commit is 11
       | hours ago.
        
         | jedimastert wrote:
         | It looks like the first commit was just a squash and merge, I
         | probably would never trust a public commit history as some kind
         | of source of truth anyways. I'm curious what your issue is?
        
           | lafrenierejm wrote:
           | > I probably would never trust a public commit history as
           | some kind of source of truth
           | 
           | What _would_ you trust as a source of truth for source code
           | if not a public commit log? I agree that a squash commit's
           | timestamp in particular ought not be taken as authoritative
           | for all of the changes in the commit, but commit history in
           | general feels like the highest quality data most projects
           | will ever have.
        
             | thejazzman wrote:
             | Until you realize it's trivial for an LLM to fabricate it
             | in about a minute
        
             | fragmede wrote:
             | I really hate when cryptocurrency has valid applications
             | but in this case, you're looking for a public adversarial
             | append only log system which is what a blockchain is.
        
       | brendank310 wrote:
       | 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
        
       | politelemon wrote:
       | Please don't use or suggest using homebrew as a Linux
       | installation solution. It's better to simply point at the
       | binaries directly.
        
         | jbreckmckye wrote:
         | What's wrong with Brew?
        
         | frenzcan wrote:
         | What's the issue with homebrew?
        
           | astrea wrote:
           | It's specifically a Mac workaround package manager. There's
           | better/cleaner ways to do it on Linux.
        
         | colesantiago wrote:
         | What's the problem with Homebrew?
         | 
         | > It's better to simply point at the binaries directly.
         | 
         | Binaries aren't at all signed and can be malicious and do
         | dangerous things.
         | 
         | Especially if it's using curl | bash to install binaries.
        
           | -mlv wrote:
           | I had some issues with brew breaking up my system and pkg-
           | config.
        
             | colesantiago wrote:
             | It is a bit hard to know what the issue is here.
             | 
             | But on average brew is much more safer than downloading a
             | binary from the ether where we don't know what it does.
             | 
             | I see more tools use the curl | bash install pattern as
             | well, which is completely insecure and very vulnerable to
             | machines.
             | 
             | Looks like the best way to install these tools is to build
             | it yourself, i.e. make install, etc.
        
           | yoavm wrote:
           | Are you using Homebrew on Linux? Genuinely curious - I never
           | met a Linux user doing that.
        
             | embedding-shape wrote:
             | At least one other person also does:
             | 
             | > as long as I have a basic Linux environment, Homebrew,
             | and Steam
             | 
             | https://xeiaso.net/blog/2025/yotld/ (An year of the Linux
             | Desktop)
             | 
             | I guess some post-macOS users might bring it with them when
             | moving. If it works :shrug:
        
         | yarekt wrote:
         | Nice, download a random binary off the internet and give it
         | your AWS credentials.
         | 
         | Please people, inspect the source to your tools, or don't use
         | them on production accounts.
        
           | thejazzman wrote:
           | How did you install homebrew?
        
       | ktevfik wrote:
       | great work.
        
       | acedTrex wrote:
       | Yet another project post that has all the hallmarks of LLM slop,
       | how exciting for everyone to have their time wasted.
        
         | blutoot wrote:
         | So what if this was vibe-coded? How do you know this was a
         | "slop" if you did not try it?
        
           | acedTrex wrote:
           | > How do you know this was a "slop" if you did not try it?
           | 
           | Because I have eyes and can look at the code for 2 seconds.
           | It's not very difficult to check for the hallmarks of
           | careless slop code.
           | 
           | If you can't tell in a few seconds then you can continue
           | testing it out just like any actual project.
        
             | minimaxir wrote:
             | And what are those hallmarks in this case? There is no
             | heuristic that is applicable for every programming
             | language.
             | 
             | Unfortunately, ratatui requires a lot of verbose code that
             | may be indistinguishable from LLM generated code:
             | https://ratatui.rs/examples/apps/demo/
        
               | acedTrex wrote:
               | Easiest one is ridiculous comments, always a dead ringer
               | for an LLM.
               | 
               | ESPECIALLY when its from a plan and comments '// STEP 2:
               | ...'
               | 
               | Like here in this posts repo https://github.com/huseyinba
               | bal/taws/blob/2ce4e24797f7f32a52...
               | 
               | This a dead ringer for LLM slop that someone didnt even
               | care enough to go through and clean up.
               | 
               | Edit: Just to keep it going, you ever seen a human write
               | dependencies like this for a small toy tui? https://githu
               | b.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52...
               | 
               | Edit2: Sure why not, lets reimplement randomly a custom
               | jsonpath when serde_json_path exists https://github.com/h
               | useyinbabal/taws/blob/2ce4e24797f7f32a52...
        
               | minimaxir wrote:
               | That's not a smoking gun. I've definitely seen pre-2023
               | open source code mentioning steps in their comments. Even
               | though that file also has a lot of tautological comments
               | which are more indicative of LLM coding, it's not a
               | smoking gun either: the frequency of comments is an
               | editorial decision which has pros and cons.
               | 
               | It's the equivalent of calling something an AI generated
               | images just because the fingers are weird, and requires a
               | judgment more concrete than "I have eyes."
               | 
               | > you ever seen a human write dependencies like this for
               | a small toy tui?
               | 
               | Yes? That's just TOML syntax. I'm not sure which
               | dependency in that list is excessive, especially for
               | something that has to handle HTTP requests. If you mean
               | adding a comment header for each section, then that's a
               | better argument, but see argument above.
        
               | acedTrex wrote:
               | I mean if you want bury your head in the sand and try to
               | play semantics over if its ENOUGH proof or not go right
               | ahead.
               | 
               | But it's more than LLM enough for anyone who has
               | experience with them to conclude the LLM drove the
               | majority of the output. Hence, slop
        
               | mahogany wrote:
               | The more you see and review LLM-generated code, the more
               | you can detect its fingerprints. Obviously you're not
               | going to prove this is LLM-generated. I wouldn't bet $1M
               | that it is. This could be 100% human made.
               | 
               | But read the same link from above: https://github.com/hus
               | eyinbabal/taws/blob/2ce4e24797f7f32a52.... LLMs leave
               | temporal comments like "// Now do X", or "// Do X using
               | the new Y", as responses to prompts like "Can you do X
               | with Y instead?".
               | 
               | or below: "// Auto-refresh every 5 seconds (only in
               | Normal mode)". I would guess this comment was during a
               | response to a prompt like: "can you only auto-refresh in
               | Normal mode?"
               | 
               | I like the gem comment from: https://github.com/huseyinba
               | bal/taws/blob/2ce4e24797f7f32a52...
               | 
               | ``` // Get log file path
               | 
               | let log_path = get_log_path(); ```
               | 
               | Sometimes there are tautological comments and sometimes
               | not. A lack of consistency is another signal.
               | 
               | No, none of these are a smoking gun. Also none of this
               | means it was completely vibe coded. To me personally, the
               | worrying part is that these patterns signal that perhaps
               | human eyes were never on that section of the code, or at
               | least the code was not thought about deeply. For a toy
               | app, who cares? For something that ingests your AWS
               | creds, I'd pass.
        
               | justamaze wrote:
               | Touch grass.
               | 
               | The snark over reimplementing things from the younger
               | crowd that reimplemented databases (mongo is webscale!),
               | operating systems (nice browser), and UI toolkits (make
               | your css that looks like win32!) as if there is a "one
               | true way" to capture syntactically the state of a machine
               | is sad.
               | 
               | You still use cobol and fortran and c or reimplementation
               | of old ideas in the form of ruby and typescript?
               | 
               | Yes yes; we've seen others stand on a soap box and
               | broadcast how the syntax must not be shuffled around.
               | Thanks for reminding us about the giant foots wrath.
               | 
               | New generation of Eric S Raymonds. Don't go down the dark
               | path!
        
           | satvikpendem wrote:
           | Vibe code is by definition slop.
        
             | acedTrex wrote:
             | They are indeed synonyms
        
           | llimllib wrote:
           | I'm not generally opposed to vibe-coded tools, I've even
           | created some.
           | 
           | However I wouldn't be excited to trust one with my AWS key
           | and read/write access to my infra
        
             | rvz wrote:
             | Especially if it is has zero tests.
        
               | minimaxir wrote:
               | Zero tests are actually a better argument that it's not
               | AI generated. Agents love tests.
        
       | Yanael wrote:
       | Nice, I was looking for this type of project 2 weeks ago. As a
       | K9s user I wanted a similar experience to manage AWS resources.
        
       | jbreckmckye wrote:
       | Interesting, looks like k9s... but for AWS
        
         | jedimastert wrote:
         | That was my first thought too, it looks like it was directly
         | inspired by k9s according to the bottom of the readme.
        
       | mikert89 wrote:
       | claude code can do this, natively without a custom implementation
        
       | ronbenton wrote:
       | I thought the title meant the AWS UI was "terminal", which I
       | would be on board with
        
       | lherron wrote:
       | Somehow every 15 line shell script I write now turns into a
       | 50kloc bun cli or tui app. Apparently there are many such cases.
        
         | toomuchtodo wrote:
         | Terminal electron.
        
       ___________________________________________________________________
       (page generated 2026-01-04 23:00 UTC)