diff --git a/dynamo-backup-to-s3/Dockerfile b/dynamo-backup-to-s3/Dockerfile new file mode 100644 index 0000000..652b0d5 --- /dev/null +++ b/dynamo-backup-to-s3/Dockerfile @@ -0,0 +1,8 @@ +FROM alpine:3.2 + +MAINTAINER Ric Lister + +RUN apk add --update nodejs && \ + npm install dynamo-backup-to-s3 -g + +ENTRYPOINT [ "dynamo-backup-to-s3" ] diff --git a/dynamo-backup-to-s3/README.md b/dynamo-backup-to-s3/README.md new file mode 100644 index 0000000..0154697 --- /dev/null +++ b/dynamo-backup-to-s3/README.md @@ -0,0 +1,19 @@ +# dynamo-backup-to-s3 + +This is a minimal image built on Alpine Linux and nodejs to run +[dynamo-backup-to-s3](https://github.com/markitx/dynamo-backup-to-s3). + +## Usage + +``` +docker run -d --name dynamo-backup-to-s3 \ + -e AWS_ACCESS_KEY_ID \ + -e AWS_SECRET_ACCESS_KEY \ + -e AWS_DEFAULT_REGION \ + rlister/dynamo-backup-to-s3:latest \ + -b my-s3-bucket/path \ + table1,table2,... +``` + +It is generally preferable to deploy to an ec2 instance with a +suitable IAM role rather than passing AWS secrets in the environment.