Setting up Amazon S3

hosting-services

#1

Duplicati can make backups to Amazon S3 storage. To set it up, follow these steps.

  1. Add a new backup
  2. Choose “Amazon S3” as the Storage type
  3. Set these parameters
    • Server: leave the default “Amazon S3”
    • Bucket name: enter the name of a bucket. If the bucket does not exist, it will be created for you. (be careful on naming - eg. no underscores allowed!)
    • Bucket create region: Choose where the bucket will be created. Note that if the bucket is already created, this setting has no effect.
    • Keep the “Standard” storage class unless you know the risks and prices
    • If you intend to store more than one backup in the bucket, enter a folder name here, otherwise leave it empty. Deep folder structures can be created by inserting /, like rootfolder/subfolder/targetfolder.
    • AWS Access ID: supply the AWS access ID to use (find it in the AWS console - top right menu with account name listed as “My security credentials” then “Access Keys” )
    • AWS Access Key: supply the AWS access Key to use (find it in the AWS console)
  4. Optionally, click the “Generate IAM access policy” button to have Duplicati set up a new user that only has access to the bucket you supply. Doing this ensures that access to the Duplicati settings does not compromise your AWS account. If you use the “Test Connection” button, Duplicati will also check if you are using an account with too many permissions and ask to set up an IAM user automatically.

Thats it. You are now ready to back up to Amazon S3. The final setup should look like this:


Ability to set personal defaults
#2

Maybe it will be usefull for someone.

If you’ve just created an empry bucket and there are no files in it, the Duplicati WILL NOT find this bucket. You have to upload any small file to the bucket from amazon consone first.


#3

Strange, I didn’t have that issue. What version of Duplicati?


#4
You are currently running Duplicati - 2.0.3.9_canary_2018-06-30

this one


#5

I think this is caused by the way the Amazon S3 buckets are mapped via DNS.

Due to delays in DNS propagation, the bucket does not work immediately after being created. After a little while, the DNS settings are updated and it starts working.

If you upload a file through the Amazon interface, maybe that is enough delay for it to start working.