containerized-awscli

Status

Run awscli or s3cmd in a container. This tooling is released under the Apache 2.0 license.

Table of Contents

• Motivation
• Pre-requisites
• Usage
• Installation
  • Antigen
  • Oh-My-Zsh
  • Zgen
  • Without a framework, or for bash users

Motivation

The security software malware on my work machine frequently breaks the aws and s3cmd commands when they tweak the settings. I need them for work, so I built a container they can't break.

Running them in a Docker container sans malware has an added benefit by providing updates to new versions faster than brew updates does.

Pre-requisites

• You need to install Docker.
• You need AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID set in your environment

Usage

Use c-aws in your shell instead of aws. c-aws passes any arguments to aws run inside the container.

Installation

Antigen

Add antigen bundle unixorn/containerized-awscli to your .zshrc with your other bundle commands.

Antigen will handle cloning the plugin for you automatically the next time you start zsh. You can also add the plugin to a running ZSH session with antigen bundle unixorn/containerized-awscli for testing before adding it to your .zshrc.

Oh-My-Zsh

1. cd ~/.oh-my-zsh/custom/plugins
2. git clone [email protected]:unixorn/containerized-awscli.git containerized-awscli
3. Add tumult to your plugin list - edit ~.zshrc and change plugins=(...) to plugins=(... containerized-awscli)

Zgen

Add zgen load unixorn/containerized-awscli to your .zshrc file in the same function you're doing your other zgen load calls in. Zgen will handle automatically cloning the plugin for you the next time you do a zgen save.

Without a framework, or for bash users

1. git clone this repository
2. Add /path/to/repository/bin to your $PATH