A terminal user interface (TUI) for interacting with AWS services, inspired by lazygit.

Beta — This project is under active development. Expect rough edges and breaking changes.

Built with ratatui + crossterm.

• ECS — Browse clusters, services, tasks, and containers. Force new deployments, stop tasks, exec into containers
• SSM — List EC2 instances with SSM agent, start interactive sessions
• CloudWatch Logs — Browse log groups and streams, live tail in real-time, run Logs Insights queries with templates
• RDS — Browse RDS/Aurora instances, connect via direct or SSM tunnel, run SQL queries in-TUI, browse tables, export results to CSV, import SQL files
• Profile management — Switch AWS profiles on the fly, automatic SSO login for SSO profiles
• Search — Filter any list with / (clusters, services, tasks, log groups, query results...)
• Copy — Press y to copy ARNs, IDs, table names, or query result rows to clipboard
• Light/Dark theme — Auto-detects terminal background, toggle with Ctrl+L

• Rust (stable)
• AWS CLI v2 installed and configured
• session-manager-plugin (optional, required for ECS exec, SSM sessions, and RDS SSM tunnels — lazy-aws can install it for you)
• mysql CLI client (optional, required for the RDS tab — mysql-client or mariadb-client package)

Pre-built binaries are available on the releases page.

Download the archive matching your platform, extract it, and move the binary to a directory in your PATH:

# Example for Linux x86_64 — adjust the version and asset name as needed
curl -L https://github.com/your-user/lazy-aws/releases/latest/download/lazy-aws-linux-x86_64.tar.gz \
  | tar -xz
mv lazy-aws ~/.local/bin/

Available assets: lazy-aws-linux-x86_64, lazy-aws-linux-aarch64, lazy-aws-macos-x86_64, lazy-aws-macos-aarch64.

git clone https://github.com/your-user/lazy-aws.git
cd lazy-aws
cargo build --release

The binary will be at ./target/release/lazy-aws.

cp ./target/release/lazy-aws ~/.local/bin/

Make sure ~/.local/bin is in your PATH. If not, add this to your shell config:

export PATH="$HOME/.local/bin:$PATH"

# Launch and select a profile interactively
lazy-aws

# Launch with a specific profile and region
lazy-aws --profile my-profile --region eu-west-1

# Force light theme
lazy-aws --light

On first launch without arguments, a profile selector appears. If the selected profile uses SSO, the SSO login is triggered automatically.

By default, lazy-aws looks for aws in your PATH. To use a different binary:

AWS_CLI_BIN=/usr/local/bin/aws lazy-aws

lazy-aws respects the standard AWS environment variables:

• AWS_PROFILE — default profile
• AWS_REGION / AWS_DEFAULT_REGION — default region

When switching profiles, the region is automatically resolved from ~/.aws/config (region or sso_region field).

When connecting to an RDS instance, lazy-aws offers to save the credentials. They are stored in:

~/.config/lazy-aws/credentials.json

The file is created with 0600 permissions (owner read/write only). Passwords are base64-encoded (not stored in plain text). Credentials are organized by AWS profile and instance:

{
  "profiles": {
    "my-profile": {
      "rds": {
        "my-db-instance": {
          "username": "admin",
          "password": "base64-encoded",
          "database": "mydb"
        }
      }
    }
  }
}

On subsequent connections, saved credentials are used automatically.

Press Ctrl+E in the query editor to pick from common templates:

cargo build             # Debug build
cargo build --release   # Release build
cargo test              # Run all tests
cargo clippy            # Lint

Debug logs are written to ~/.local/state/lazy-aws/debug.log.

src/
├── aws/            # Domain layer (no UI dependency)
│   ├── types.rs    # Cluster, Service, Task, Container, Instance, LogGroup...
│   ├── exec.rs     # Executor trait, RealExecutor, streaming
│   └── runner.rs   # Typed wrapper over AWS CLI
├── config/         # Config resolution, binary validation
├── credentials.rs  # Saved RDS credentials (load/save, base64 encode/decode)
├── logger/         # File logger (~/.local/state/lazy-aws/debug.log)
└── ui/
    ├── app.rs      # Event loop, async loading, key routing
    ├── style/      # Color theme (dark/light) + style functions
    ├── components/ # TabBar, StatusBar, ConfirmDialog, InputBox, Spinner, Help
    └── panels/     # Clusters, Services, Tasks, Containers, Instances,
                    # LogGroups, LogStreams, LogViewer, Detail, Output, Terminal,
                    # RdsInstances, RdsTables, QueryResults

All data loading is asynchronous (background threads + mpsc channels) so the UI stays responsive. Each AWS call runs in its own thread — if one fails, the others continue.

MIT