Docker image of the latest and greatest of AWS tools, always.
2.0K
Docker image of the latest and greatest of AWS tools, always.
# Configure aws inside the container only
$ docker run --rm -it flemay/aws bash
$> aws configure
# Run image with env vars (useful when using assume role)
$ docker run --rm -it \
-e "AWS_ACCESS_KEY_ID" \
-e "AWS_SECRET_ACCESS_KEY" \
-e "AWS_SESSION_TOKEN" \
-e "AWS_SECURITY_TOKEN" \
-e "ASSUMED_ROLE" \
-e "AWS_REGION" \
-e "AWS_DEFAULT_REGION" \
-e "AWS_PROFILE" \
-v ~/.aws:/root/.aws \
-v $(PWD):/opt/app:Z -w /opt/app \
flemay/aws bash
# Create a new AWS profile
$ docker run --rm -it -v /path/to/.aws:/root/.aws flemay/aws bash
$> aws configure --profile my-user-profile
AWS Access Key ID [None]: key
AWS Secret Access Key [None]: secret
Default region name [None]: ap-southeast-2
Default output format [None]:
# Query - list all function names that run on NodeJS 6.10
$> aws lambda list-functions --region ap-southeast-2 --query Functions[?Runtime=="'nodejs6.10'"].FunctionName | sort
# Build image locally
# generate .env file
$ make envfile
# build image
$ make build
# test image
$ make test
# go inside the container
$ make shell
This image will always be built with the tag latest and tools will always be up to date. This may cause issues if any tool has a breaking change.
A change to master triggers a GitHub Action that builds, tests, and pushes the image to Docker Hub. The automatic build on Docker Hub has been disabled ensuring the build process to only go through GitHub Actions. Moreover, to make sure the image is always up to date, a scheduled GitHub Action kicks off every month. Finally, a pull request triggers another GitHub Action which builds and tests the image.
Contributions are greatly appreciated. Everyone can contribute and here are different ways.
Content type
Image
Digest
sha256:1cb43bada…
Size
159.3 MB
Last updated
about 4 years ago
docker pull flemay/aws