Add AWS s3 v4 auth mechanism fix

Author: iamgalba

README.md

@@ -2,6 +2,16 @@
 
 This image runs mongodump to backup data using cronjob to an s3 bucket
 
+## Forked from [halvves/mongodb-backup-s3](https://github.com/halvves/mongodb-backup-s3)
+
+Added support for AWS S3 v4 authorization mechanism for those who are experiencing error:
+
+```
+A client error (InvalidRequest) occurred when calling the PutObject operation: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
+```
+
+Play well with this docker [nginx-letsencrypt-mongo-portainer] setup
+
 ## Usage:
 
 ```
@@ -13,10 +23,10 @@ docker run -d \
   --env MONGODB_PORT=27017 \
   --env MONGODB_USER=admin \
   --env MONGODB_PASS=password \
-  halvves/mongodb-backup-s3
+  deenoize/mongodb-backup-s3
 ```
 
-If you link `halvves/mongodb-backup-s3` to a mongodb container with an alias named mongodb, this image will try to auto load the `host`, `port`, `user`, `pass` if possible. Like this:
+If you link `deenoize/mongodb-backup-s3` to a mongodb container with an alias named mongodb, this image will try to auto load the `host`, `port`, `user`, `pass` if possible. Like this:
 
 ```
 docker run -d \
@@ -26,15 +36,15 @@ docker run -d \
   --env BACKUP_FOLDER=a/sub/folder/path/ \
   --env INIT_BACKUP=true \
   --link my_mongo_db:mongodb \
-  halvves/mongodb-backup-s3
+  deenoize/mongodb-backup-s3
 ```
 
 Add to a docker-compose.yml to enhance your robotic army:
 
 For automated backups
 ```
 mongodbbackup:
-  image: 'halvves/mongodb-backup-s3:latest'
+  image: 'deenoize/mongodb-backup-s3:latest'
   links:
     - mongodb
   environment:
@@ -48,7 +58,7 @@ mongodbbackup:
 Or use `INIT_RESTORE` with `DISABLE_CRON` for seeding/restoring/starting a db (great for a fresh instance or a dev machine)
 ```
 mongodbbackup:
-  image: 'halvves/mongodb-backup-s3:latest'
+  image: 'deenoize/mongodb-backup-s3:latest'
   links:
     - mongodb
   environment:
@@ -114,4 +124,4 @@ docker exec mongodb-backup-s3 /restore.sh
 
 ## Acknowledgements
 
-  * forked from [futurist](https://github.com/futurist)'s fork of [tutumcloud/mongodb-backup](https://github.com/tutumcloud/mongodb-backup)
+  * forked from [halvves/mongodb-backup-s3](https://github.com/halvves/mongodb-backup-s3) fork of [futurist](https://github.com/futurist)'s fork of [tutumcloud/mongodb-backup](https://github.com/tutumcloud/mongodb-backup)

run.sh

@@ -26,6 +26,7 @@ TIMESTAMP=\`/bin/date +"%Y%m%dT%H%M%S"\`
 BACKUP_NAME=\${TIMESTAMP}.dump.gz
 S3BACKUP=${S3PATH}\${BACKUP_NAME}
 S3LATEST=${S3PATH}latest.dump.gz
+aws configure set default.s3.signature_version s3v4
 echo "=> Backup started"
 if mongodump --host ${MONGODB_HOST} --port ${MONGODB_PORT} ${USER_STR}${PASS_STR}${DB_STR} --archive=\${BACKUP_NAME} --gzip ${EXTRA_OPTS} && aws s3 cp \${BACKUP_NAME} \${S3BACKUP} && aws s3 cp \${S3BACKUP} \${S3LATEST} && rm \${BACKUP_NAME} ;then
     echo "   > Backup succeeded"
@@ -47,6 +48,7 @@ else
     RESTORE_ME=latest.dump.gz
 fi
 S3RESTORE=${S3PATH}\${RESTORE_ME}
+aws configure set default.s3.signature_version s3v4
 echo "=> Restore database from \${RESTORE_ME}"
 if aws s3 cp \${S3RESTORE} \${RESTORE_ME} && mongorestore --host ${MONGODB_HOST} --port ${MONGODB_PORT} ${USER_STR}${PASS_STR}${DB_STR} --drop --archive=\${RESTORE_ME} --gzip && rm \${RESTORE_ME}; then
     echo "   Restore succeeded"