Skip to content
Permalink
Browse files
Closes #260
Use the official AWS CLI instead of s3cmd

Based on this comment: #258 (comment)

Note: I checked the docs and this is the only place where we suggested to use `s3cmd`
  • Loading branch information
duncangrant committed Jun 21, 2018
2 parents f63a2dc + 2a8ae61 commit 29c11688ac6330c22ea7a497dd1c3a9edf6f889c
Showing 1 changed file with 4 additions and 4 deletions.
@@ -230,8 +230,8 @@ An example script to be invoked by CRON is shown below:
DATA_DIR=/path/to/base/dir/data

tar --exclude '*/backups/*' -czvf $BACKUP_FILENAME $DATA_DIR
# For s3cmd installation see http://s3tools.org/repositories
s3cmd put $BACKUP_FILENAME s3://mybackupbucket
# For AWS CLI installation see https://aws.amazon.com/cli
aws s3 cp $BACKUP_FILENAME s3://mybackupbucket
rm $BACKUP_FILENAME


@@ -255,7 +255,7 @@ An example script to be invoked by CRON is shown below:
https://${HOSTNAME}:8443/v1/server/ha/persist/export \
> ${BACKUP_FILENAME}
# For s3cmd installation see http://s3tools.org/repositories
s3cmd put $BACKUP_FILENAME s3://mybackupbucket
# For AWS CLI installation see https://aws.amazon.com/cli
aws s3 cp $BACKUP_FILENAME s3://mybackupbucket
rm $BACKUP_FILENAME

0 comments on commit 29c1168

Please sign in to comment.