Lazy AWS

Lazy AWS is a keyboard-driven home for your AWS resources, delivered as a terminal application. Instead of moving between browser tabs, it lets you browse, inspect, and act on your cloud resources without leaving the keyboard. The product positions itself as a single terminal window where your account and region stay in view while you move through services, panes, and resource lists. According to its website, the tool covers services such as EC2, ECS, ECR, S3, and Lambda, and lets you run AWS CLI actions after reviewing exactly what will execute. It is aimed at people who already work in a terminal and want a faster, less click-heavy way to look at what is running in their AWS account. The problem Lazy AWS addresses is described on its site as the console shuffle — the constant switching, clicking, and context shifting involved in working with AWS resources through a graphical console. The site frames its value as a small learning curve and a lot less clicking, suggesting a tool that is quick to learn but removes repetitive pointer work. Rather than replacing the AWS CLI, Lazy AWS sits on top of an existing AWS CLI setup and adds a browsable, keyboard-first interface over it. That matters for developers and operators who already know their way around AWS CLI profiles and regions but want a faster way to see what exists in an account, dig into a specific resource, and then take a deliberate action against it. The first step in the product's three-stop tour is finding your bearings. In this mode you switch between services, move between panes, and select a resource, while your account and region stay visible on screen. The demo screenshots show EC2 as an example, with instance, volume, security group, and subnet panes displayed alongside JSON details for the selected resource. Keeping the account and region in view matters because those two pieces of context determine which resources you are actually looking at; having them permanently on screen reduces the risk of acting in the wrong account or region. Switching services and panes from the keyboard means the whole navigation loop stays on the keyboard rather than moving to a mouse. The second stop is going one level deeper. You can filter a list and then open the selected resource's JSON details, with related resources shown right beside it. This is where Lazy AWS differs from a plain list view: the JSON detail pane gives you the full shape of a resource, while the neighbouring panes give you the things connected to it. In the EC2 example on the site, that means seeing an instance together with its volume, security group, and subnet information rather than chasing each one separately. Filtering a list first is the mechanism the product uses to narrow down large resource collections before you commit to opening one. The third stop is knowing what will run. When you open an action, Lazy AWS shows you the account, the target, and the exact AWS CLI command before anything executes, and runs it only when you confirm. This confirmation step is the product's core safety mechanism: it turns an action into something you review rather than something that fires immediately. Because the exact CLI command is displayed, you can see precisely which AWS CLI operation is about to be issued against which target, in which account. That is useful both for people who already know the CLI and for people who are learning it, since the command itself is visible on screen as part of the confirmation step. Lazy AWS installs as a binary. The site lists two installation routes: a curl script that installs the binary to ~/.local/bin, which you add to your PATH if needed, and a Homebrew tap for macOS or Linux. Supported systems are macOS, Ubuntu, Arch Linux, and Omarchy; Windows is not supported, and Debian installs are available without a support guarantee. AWS CLI v2 is a prerequisite, though AWS CLI v2 and credentials are only needed when connecting your own AWS account. You can start with lazyaws --demo to run the installed demo against local sample data with no AWS account or credentials required. To connect your account you use an existing AWS CLI profile — signing in first with aws sso login --profile dev if your profile uses SSO — and then run lazyaws --profile dev --region eu-west-1. The overall approach is therefore to reuse the credentials, profiles, and regions you already have configured rather than introducing a separate authentication or configuration system. The stated benefits are speed and reduced clicking. The site summarises the learning curve as three stops — find your bearings, go one level deeper, know what will run — after which, it says, you know your way around. Because navigation is keyboard-driven, switching services and panes does not require reaching for a mouse. Because account and region stay in view, you keep the context that matters for every action. Because actions require confirmation with the exact CLI command shown, the tool builds a review step into every execution. And because the demo runs on local sample data without credentials, you can evaluate the interface before connecting a real account. Concrete workflows described on the site include browsing a service's resource list and selecting an individual resource; filtering a list to narrow it down and then opening the JSON details of the selection; and reviewing related resources displayed beside a selected resource — for example an EC2 instance next to its volume, security group, and subnet panes. Beyond inspection, the action flow covers opening an action, reviewing the account, target, and exact AWS CLI command, and confirming execution. The demo mode supports a trial workflow with no AWS account, and the profile-plus-region launch command supports working against a specific named profile and region, including SSO-based profiles that require a sign-in step first. Lazy AWS is aimed at developers and cloud practitioners who are comfortable in a terminal and already use the AWS CLI. It runs on macOS, Ubuntu, Arch Linux, and Omarchy and explicitly does not support Windows. Installation is through a curl script or a Homebrew tap, and the tool depends on AWS CLI v2 for connecting a real account. Service coverage shown on the site includes EC2, ECS, ECR, S3, and Lambda. Product Hunt lists it under Amazon, Open Source, Developer Tools, and GitHub, and the service guide is hosted in a GitHub repository. No pricing or plan information is stated on the website. In short, Lazy AWS takes the AWS resources you already have and puts them in one terminal window with keyboard navigation, side-by-side resource and JSON detail panes, and an explicit confirmation step that displays the exact AWS CLI command before it runs. Its value proposition is straightforward: your cloud, your terminal, less console shuffle and a lot less clicking.