1.11.97/latest | 1.11.96 | 1.11.94 | 1.11.92 | 1.11.91 | 1.11.90 | 1.11.89 | 1.11.88 | 1.11.85 | 1.11.84 | 1.11.80 | 1.11.78 | 1.11.77 | 1.11.76 | 1.11.74 | 1.11.72 | 1.11.71 | 1.11.70 | 1.11.69 | 1.11.68 | 1.11.67 | 1.11.65 | 1.11.64 | 1.11.63 | 1.11.61 | 1.11.59 | 1.11.58 | 1.11.56 | 1.11.51 | 1.11.50 | 1.11.49 | 1.11.48 | 1.11.46 | 1.11.45 | 1.11.43 | 1.11.41 | 1.11.39 | 1.11.36 | 1.11.33 | 1.11.30 | 1.11.28 | 1.11.26 | 1.11.25 | 1.11.24 | 1.11.23 | 1.11.22 | 1.11.21 | 1.11.20 | 1.11.18 | 1.11.16 | 1.11.15 | 1.11.14 | 1.11.13 | 1.11.12 | 1.11.11 | 1.11.10 | 1.11.9 | 1.11.8 | 1.11.7 | 1.11.6 | 1.11.5 | 1.11.4 | 1.11.3 | 1.11.1 | 1.10.65 | 1.10.64 | 1.10.61 | 1.10.60 | 1.10.58 | 1.10.57 | 1.10.56 | 1.10.55 | 1.10.54 | 1.10.53 | 1.10.52 | 1.10.51 | 1.10.50 | 1.10.49
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 -v $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