npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@vadimgodev/ecsh

v0.1.1

Published

ssh for ECS — open an interactive shell in an AWS ECS container

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

vadimgodevvadimgodev

Keywords

ecsawssshexeccliexecute-commandsession-managerfargatessm

Readme

ecsh

ssh for ECS — open an interactive shell in an AWS ECS container without copying ARNs or remembering the long aws ecs execute-command invocation.

npx @vadimgodev/ecsh   # interactive wizard: profile → cluster → service → task → container → shell

Prerequisites

ecsh discovers resources with the AWS SDK but delegates the interactive shell to the AWS CLI, so two external tools must be installed:

  1. AWS CLI v2 — https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html
  2. Session Manager plugin — https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html

| OS | AWS CLI v2 | Session Manager plugin | |---|---|---| | macOS | brew install awscli | brew install --cask session-manager-plugin | | Linux | bundled installer (see link) | .deb/.rpm or bundled installer (see link) | | Windows | MSI installer (see link) | MSI installer (see link) |

Run ecsh doctor to check your environment.

Install

npx @vadimgodev/ecsh        # no install
npm i -g @vadimgodev/ecsh   # global install (provides the `ecsh` command)

Requires Node.js ≥ 22.

Usage

ecsh                              # interactive wizard
ecsh --cluster web --service api  # pre-fill steps with flags
ecsh -- /bin/sh                   # choose the command after --

ecsh save prod-api                # run the wizard, save coordinates (no connect)
ecsh prod-api                     # connect to a saved target (resolves the live task)
ecsh prod-api --container worker  # recall a target but override one field
ecsh --save prod-api              # connect now AND remember it

ecsh ls                           # list saved targets
ecsh rm prod-api                  # delete a saved target
ecsh doctor                       # diagnose why exec might fail

Flags: --profile, --region, --cluster, --service, --task, --container, --command (or a trailing -- <cmd…>).

Precedence

  • General fields: flag > saved target > prompt (command also falls back to /bin/bash).
  • profile: --profile > target > $AWS_PROFILE > pick.
  • region: --region > target > $AWS_REGION / $AWS_DEFAULT_REGION > profile default > pick.

A saved target is self-contained: ecsh prod-api hits prod even if AWS_PROFILE=staging. A target never stores a task — it resolves the live running task at connect time, so it never goes stale across deploys.

Configuration

Saved targets live in a JSON file resolved via XDG / env-paths (~/.config/ecsh/config.json on Linux, %APPDATA%\ecsh\config.json on Windows). It is machine-written by ecsh save but safe to hand-edit.

License

MIT © Vadim Goncharov