• 2.0.5/v2/latest
• 1.18.31/v1
• 1.17.14
• 1.16.312
• 1.15.85
• 1.14.69
• 1.12.1
• 1.11.190
• 1.10.65

This image provides the AWS CLI and a few other tools, including jq.

I have an IFTT recipe written to notify me of new releases of the AWS CLI, so should be able to keep up-to-date on it.

Credentials can be provided in any of the aws-cli supported formats.

If you need to create the credentials file, you can use the aws-cli configure command by using the following command:

docker run --rm -tiv $HOME/.aws:/root/.aws mikesir87/aws-cli aws configure

From that point on, simply mount the directory containing your config.

docker run --rm -v $HOME/.aws:/root/.aws mikesir87/aws-cli aws s3 ls

This is supported, although NOT encouraged, as the environment variables can end up in command-line history, available for container inspection, etc.

• AWS_ACCESS_KEY_ID` - specify the access key ID
• AWS_SECRET_ACCESS_KEY` - the secret access key

docker run --rm -e AWS_ACCESS_KEY_ID=my-key-id -e AWS_SECRET_ACCESS_KEY=my-secret-access-key -v $(pwd):/aws mikesir87/aws-cli aws s3 ls 

You can setup an alias for aws to simply start a container, hiding the fact that it's not actually installed on the machine. Then, updating the version simply becomes a docker pull mikesir87/aws-cli.

alias aws='docker run --rm -tiv $HOME/.aws:/root/.aws -v $(pwd):/aws mikesir87/aws-cli aws'