Sign inSign up

zenoss/aws-cli

By zenoss

•Updated about 9 years ago

aws-cli + jq

Image
0

1.9K

zenoss/aws-cli repository overview

⁠AWS CLI in Docker

AWS CLI docker container with a few scripts to help with ZING deployments.

⁠Build

docker build -t zenoss/aws-cli .

Automated build on Docker Hub

DockerHub Badge

⁠Usage

Environment vars with AWS credentials must be set for each command:

AWS_ACCESS_KEY_ID="<id>"
AWS_SECRETY_ACCESS_KEY="<key>"
AWS_DEFAULT_REGION="<region>"

You can use regular aws commands as follows:

docker run --rm -t \
    -e "AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID" \
    -e "AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY" \
    -e "AWS_DEFAULT_REGION=$AWS_DEFAULT_REGION" \
    -v "$PWD:/project" \
    zenoss/aws-cli \
    aws s3 sync /project s3://staging.zing.ninja --delete

There are also a few (one?) helper script(s) which can be run as follows:

docker run --rm -t \
    -e "AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID" \
    -e "AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY" \
    -e "AWS_DEFAULT_REGION=$AWS_DEFAULT_REGION" \
    -v "$PWD:/project" \
    zenoss/aws-cli \
    invalidate-n-wait.sh S11A16G5KZMEQD "/assets/* /js/* /css/app.css"

Or, the primary reason this image was created, s3 sync, invalidate, and wait:

docker run --rm -t \
    -e "AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID" \
    -e "AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY" \
    -e "AWS_DEFAULT_REGION=$AWS_DEFAULT_REGION" \
    -v "$PWD:/project" \
    zenoss/aws-cli \
	/bin/sh -c "aws s3 sync /project s3://staging.zing.ninja --delete && invalidate-n-wait.sh S11A16G5KZMEQD \"/*\""

⁠Helper Scripts

> invalidate-n-wait.sh --help
Usage: invalidate-n-wait.sh DISTRIBUTION_ID "PATHS"
Creates an invalidation for AWS Cloudfront for PATHS, and waits for completion

Example:
  invalidate-n-wait.sh S11A16G5KZMEQD "/assets/* /js/* /css/app.css"

⁠References

AWS CLI Docs: https://aws.amazon.com/documentation/cli/⁠

Tag summary

Content type

Image

Digest

Size

27.8 MB

Last updated

about 9 years ago

docker pull zenoss/aws-cli