Lazy AWS

Lazy AWS is a keyboard-driven terminal interface for a user’s AWS resources. The website describes it as “your cloud, your terminal” and as “a keyboard-driven home for your AWS resources.” Its main purpose is to let users browse, inspect, and act on AWS resources without the console shuffle. Users can switch services, move between panes, select a resource, filter lists, open JSON details, and review actions from one terminal. The product keeps the account and region in view while users work. It is presented for people who prefer keyboard-driven workflows and want AWS resource browsing and AWS CLI actions to happen in the same terminal environment. The site frames the experience as three steps: find your bearings, go one level deeper, and know what will run. Lazy AWS is therefore a terminal home for browsing resources and running confirmed AWS CLI actions rather than a replacement for the AWS CLI or a web console. The background problem is the console shuffle and command context. AWS resources are often managed through a web console, which involves clicking through screens; the site says Lazy AWS offers “a lot less clicking” and “without the console shuffle.” The AWS CLI is powerful, but users need to know commands and targets. Lazy AWS places resource browsing in the terminal, then shows the exact AWS CLI command before execution. This addresses both navigation effort and command visibility. It matters because users can lose context when moving between console pages, and because actions need a clear target. Lazy AWS keeps account, region, resource details, and command confirmation in one terminal flow. The site describes a small learning curve and a shorter path to getting work done. The first feature group is keyboard-driven browsing and pane navigation. Users switch services, move between panes, and select a resource while the account and region stay in view. The site’s demo captures show resource lists beside the selected resource’s JSON details. The page displays icons for EC2, ECS, ECR, S3, and Lambda, and includes an EC2 demo with instance, volume, security group, and subnet panes. This pane layout keeps a resource list, its details, and related resources visible together. Users can filter a list and then open the selected resource’s JSON details. The site calls this “go one level deeper”: filter a list, open JSON details, and see related resources beside it. This is useful because users can inspect a resource and its associations without leaving the terminal or jumping to separate screens. The second feature group is confirmed actions. Users can open an action and review the account, the target, and the exact AWS CLI command. The action runs only when the user confirms it. The site presents this as “know what will run.” This workflow is explicitly designed to make execution visible before it happens. Instead of hiding the CLI, Lazy AWS shows the command that will be used. The confirmation view includes the account and target, so users can check where the action will apply. This is useful for reducing accidental actions and for learning or verifying the underlying AWS CLI command. The site says users can “run confirmed AWS CLI actions without leaving your keyboard,” tying action execution directly to the terminal workflow. The third feature group is setup, demo, and account connection. Lazy AWS supports macOS, Ubuntu, Arch Linux, and Omarchy; Windows is not supported. Users need AWS CLI v2 before starting. Installation is available with curl or Homebrew. The curl command installs the binary to ~/.local/bin, and users add that directory to PATH if needed. The Homebrew command installs from the capybara-brain346 tap. After installation, users can run the installed demo with local sample data, with no AWS account or credentials needed. To connect an account, users provide an existing AWS CLI profile, for example lazyaws --profile dev --region eu-west-1. If the profile uses SSO, users sign in first with aws sso login --profile dev. Debian installs are available without a support guarantee. This setup path lets users try the interface before connecting real resources. Overall, Lazy AWS combines a terminal resource browser with the AWS CLI. The website describes three stops: find your bearings by switching services and selecting resources; go one level deeper by filtering and opening JSON details with related resources beside them; and know what will run by reviewing the account, target, and exact CLI command before confirmation. The unique approach is that browsing and action stay in one keyboard-driven terminal. Resource lists appear beside the selected resource’s JSON details, and actions show the AWS CLI command rather than executing invisibly. The product uses AWS CLI profiles and credentials for account access, while the demo uses local sample data. The site emphasizes a small learning curve and less clicking, with the terminal as the home for browsing, inspecting, and acting. The stated benefits are less setup, more getting things done, a small learning curve, and a lot less clicking. Users can keep their account and region in view, move through resource panes by keyboard, inspect JSON details, see related resources, and run AWS CLI actions only after confirmation. The demo provides a no-credentials way to learn the workflow. Because the exact AWS CLI command is shown before execution, users can see what will run and verify the target. The site’s three-step tour is intended to help users learn the interface quickly: find bearings, inspect details, and confirm actions. These outcomes are presented as a way to reduce console shuffling and keep AWS resource work in the terminal. Concrete use cases include browsing AWS resources from a terminal while keeping account and region visible; switching between services such as the services shown by icons and selecting a resource; filtering a resource list and opening the selected resource’s JSON details; reviewing related resources beside the details, such as EC2 instance, volume, security group, and subnet panes; opening an action to review the account, target, and exact AWS CLI command before confirming execution; running the local demo to explore the interface without an AWS account or credentials; and connecting an existing AWS CLI profile, including an SSO profile after aws sso login. The site’s examples center on the EC2 demo and general service switching. The workflow is designed for terminal users who want to browse, inspect, and act without moving to the AWS console. The target users are people who work with AWS resources from a terminal and prefer keyboard-driven navigation, including developers and cloud practitioners who already use AWS CLI profiles and credentials. The site positions Lazy AWS as a home for AWS resources in the terminal, with support for macOS, Ubuntu, Arch Linux, and Omarchy and no Windows support. The content mentions AWS CLI v2, AWS CLI profiles, SSO login, and account and region context. The Product Hunt listing categorizes it under Amazon, Open Source, Developer Tools, and GitHub, and the site links to a GitHub service guide. Pricing is not stated in the provided content. Lazy AWS’s primary value proposition is a keyboard-driven terminal home for AWS resources: browse, inspect, and act without the console shuffle, with account and region in view and exact AWS CLI commands confirmed before they run. It keeps resource lists, JSON details, related resources, and action confirmation in one terminal workflow, while offering a no-credentials demo and AWS CLI profile connection. For terminal-oriented AWS users on supported macOS and Linux environments, it aims to reduce clicking and make actions visible before execution.