e1s is a terminal application to easily browse and manage AWS ECS resources, supports both Fargate and EC2 ECS launch types. Inspired by k9s.

e1s uses the default aws-cli configuration. It does not store or send your access key or secret key anywhere. Credentials are only used to securely connect to AWS APIs through the AWS SDK for Go.

You can choose AWS credentials and target region in three ways:

• Use your default AWS CLI profile and region.
• Override them at startup with AWS_PROFILE, AWS_REGION, --profile, or --region.
• Switch them while e1s is running with Ctrl+P for profiles and Ctrl+R for regions.

e1s reads local AWS shared config and credentials files, so it works with common setups such as static credentials, assume-role profiles, credential_process, and AWS IAM Identity Center or SSO-based configurations.

e1s is available on Linux, macOS and Windows platforms.

• Binaries for Linux, Windows and Mac are available in the release page.
• Homebrew for macOS or Linux

brew install keidarcy/tap/e1s
# brew upgrade
# brew upgrade keidarcy/tap/e1s

• Docker image

# docker image
docker pull ghcr.io/keidarcy/e1s:latest

• AWS CloudShell(Good for quick tryout)

curl -sL https://raw.githubusercontent.com/keidarcy/e1s-install/master/cloudshell-install.sh | bash

• go install command

go install github.com/keidarcy/e1s/cmd/e1s@latest

• asdf-vm

asdf plugin add e1s
asdf install e1s latest
asdf global e1s latest

• mise

mise install e1s@latest

Make sure you have the AWS CLI installed and properly configured with the necessary permissions to access your ECS resources, and session manager plugin installed if you want to use the interactive exec or port forwarding features.

• Usage of e1s:

$ e1s -h
e1s is a terminal application to easily browse and manage AWS ECS resources 🐱.
Check https://github.com/keidarcy/e1s for more details.

Usage:
  e1s [flags]

Flags:
      --cluster string       specify the default cluster
  -c, --config-file string   config file (default "$HOME/.config/e1s/config.yml")
  -d, --debug                sets debug mode
  -h, --help                 help for e1s
  -j, --json                 log output json format
  -l, --log-file string      specify the log file path (default "${TMPDIR}e1s.log")
      --profile string       specify the AWS profile
      --read-only            sets read only mode
  -r, --refresh int          specify the default refresh rate as an integer, sets -1 to stop auto refresh (sec) (default 30)
      --region string        specify the AWS region
      --service string       specify the default service (requires --cluster)
  -s, --shell string         specify interactive ecs exec shell (default "/bin/sh")
      --splash               display startup splash screen (AWS load runs before the UI) (default true)
      --theme string         specify color theme
  -v, --version              version for e1s

• Examples

# use all default config
$ e1s
# use custom-profile profile, us-east-2 region
$ AWS_PROFILE=custom-profile AWS_REGION=us-east-2 e1s
# use custom-profile profile, us-east-2 region
$ e1s --profile custom-profile --region us-east-2
# use default cluster and default service
$ e1s --cluster cluster-1 --service service-1
# use command line to set read only, debug, stop auto refresh with a custom log path, json output, and dracula theme
$ e1s --read-only --debug --refresh -1 --log-file /tmp/e1s.log --json --theme dracula
# disable the startup splash screen
$ e1s --splash=false
# docker run with specified profile and region
$ docker run -it --rm -v $HOME/.aws:/root/.aws ghcr.io/keidarcy/e1s:latest e1s --profile YOUR_PROFILE --region YOUR_REGION

Default config file path is $HOME/.config/e1s/config.yml. You can specify a different config file with --config-file. Because e1s uses viper, standard config file formats supported by viper can be used.

Typical settings you may want to manage in config are:

• theme
• refresh
• read-only
• log-file
• default cluster and service
• splash
• color overrides

Theme and colors can be specified by options or config file. Full themes list can be found here. If you prefer to use your own color theme, you can specify the colors in the config file.

colors:
  BgColor: "#272822"
  FgColor: "#f8f8f2"
  BorderColor: "#a1efe4"
  Black: "#272822"
  Red: "#f92672"
  Green: "#a6e22e"
  Yellow: "#f4bf75"
  Blue: "#66d9ef"
  Magenta: "#ae81ff"
  Cyan: "#a1efe4"
  Gray: "#808080"

colors:
  BgColor: black
  FgColor: cadeblue
  BorderColor: dodgerblue
  Black: black
  Red: orangered
  Green: palegreen
  Yellow: greenyellow
  Blue: darkslateblue
  Magenta: mediumpurple
  Cyan: lightskyblue
  Gray: lightslategray

e1s supports Vim-style navigation: use h, j, k, l for left, down, up, right navigation respectively.

Common shortcuts:

• ? shows the help page.
• Ctrl+P opens the AWS profile list.
• Ctrl+R opens the AWS region list.
• / opens table filtering. Use ESC to clear the current filter.
• F1 to F12 sort the current table by column.
• d opens the description view for the selected resource.
• b opens the selected resource in the AWS console.
• r refreshes the current view.
• s opens shell access on supported task, instance, and container views.

Press ? to check overall key bindings.

go run cmd/e1s/main.go --debug --log-file /tmp/e1s.log

tail -f /tmp/e1s.log

• Browse ECS resources in a drill-down flow: clusters -> services -> tasks -> containers.
• Jump directly to a specific cluster or service from the CLI.
• Use the app in read-only mode when you want browsing and inspection without mutation actions.
• Auto-refresh resource lists on a configurable interval.
• Start with a splash screen that loads AWS resources before the main UI is shown.

• Vim-style navigation with rich keyboard shortcuts.
• Global help page.
• In-table filtering with simple text matching or column:value syntax.
• Per-column sorting with function keys.
• Dedicated profile and region views with in-app switching.
• Footer indicators that show the current AWS profile and region context.

• Describe clusters.
• Describe EC2 container instances.
• Describe services.
• Describe service deployments.
• Describe service revisions.
• Describe tasks, including running and stopped tasks.
• Describe containers.
• Describe task definitions.
• Describe service autoscaling.
• Open the selected resource in the AWS console.
• View CloudWatch Logs for supported awslogs configurations.
• Start realtime log streaming for supported single-log-group cases.
• Show service CPU and memory metrics.

• ECS Exec style interactive shell into containers.
• Interactive shell into ECS container instances through AWS Systems Manager.
• Update services.
• Roll back service deployments.
• Stop tasks.
• Register new task definitions.
• Start local port forwarding sessions.
• Start remote host port forwarding sessions through a selected container.
• Transfer files through S3-backed workflows.
• Run one-off exec commands in containers.
• Download text file content from containers.

• Configure themes from the built-in theme set.
• Override individual colors in config.
• Adjust logging, refresh interval, splash behavior, shell, and default navigation targets.

Press / to filter rows. Use plain text to filter the first column or column:value queries (for example service:1). Press ESC to clear the filter.

Press F1 through F12 to sort the current table by that column index.

Press Ctrl+P to pick an AWS profile and Ctrl+R to pick a region. The footer shows the active profile and region.

Use aws-ecs-exec-checker to check for the pre-requisites to use ECS exec.

Use ctrl + d to exit interactive-exec session.

The execute command failed because execute command... - check service execute command, task role policy

Session Manager plugin not found - document.

• Force new deployment
• Desired tasks
• Task definition family
• Task definition revision

From the service list, press p on a service to open its deployments. From there you can inspect a deployment or open the linked service revision.

With a specified task and container, to start port forwarding session you need to specify a port and a local port. The local port is the port on your local machine that you want to use to access the container port.

With a specified task and container, to start a remote host port forwarding session you need to specify a port, a host and a local port. The local port is the port on your local machine that you want to use to access the remote host port though container.

Implemented by a S3 bucket. Since file transfer though a S3 bucket and aws-cli in container, you need a S3 bucket and add permissions S3 bucket permission to the task role and e1s role, and also need a aws-cli installed container.

If you have any feature requests or bug reports, please submit them through GitHub Issues.

• Bump version
• make tag

Xing Yahao(https://github.com/keidarcy)

• tview
• k9s
• ecsview