elken/cloud-connect-tools

A repository of tools for interacting with clouds

Cloud Connect Tools

A repo of useful tools for interacting with cloud resources in various ways.

awssh

A poorly named script to easily port-forward or SSH to an Amazon ECS container. Intended for accessing remote nREPL instances, in theory it could be used for anything.

Dependencies

• babashka
• gum
• AWS CLI
  • Including the SSM plugin

Install

The script is a self-contained babashka script, so place anywhere in your path after bb and gum and it should be fine.

Usage

awssh -- Easily port forward to an ECS container.

  -h, --help    Show this help
  -f, --forward Specify ports to forward to. Leave unset to ssh directly.

Use local:remote or 1 port for local & remote

As per the help doc, there are 3 modes of use here:

Regular SSH

In order to just connect to an ECS container, run without any arguments and select the container from the list.

Port forward on the same port

For this, pass the -f flag with a single port and that port will be used to forward both remotely and locally

Port forward on different ports

For this, pass the -f flag with a portspec like 2222:8080 which will create a forward from the local port 2222 to the remote port 8080

kubecon

Similar to awssh, this allows you to run an arbitrary command on a pod.

Dependencies

• babashka
• gum
• kubectl (setup for this is outside the scope of this project)

Install

The script is a self-contained babashka script, so place anywhere in your path after bb and gum and it should be fine.

Usage

kubecon -- Run a command for a pod.

  -h, --help  Show this help
  -f, --force Delete the caches and re-fetch all cached data

The bulk of the usage is just following the prompts. Namespaces and deployments remember the previously selected values, whereas the command history isn’t persisted (as this could leak secrets or other sensitive information)