Support regional S3 access

Bug #548632 reported by Richard Hughes
This bug affects 15 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Won't Fix

Bug Description

I like in the UK, and need to use the --s3-european-buckets option to duplicity. I would love to use deja-dup, but this option can't be passed as an environment variable and there's no checkbox in the UI. One checkbox and one option would make my life much easier. Thanks!

Michael Terry (mterry)
summary: - Doesn't sync with my s3 instance
+ Support regional S3 access
Changed in deja-dup:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

There's now also an Asian (Singapore) region.

Michael Terry (mterry)
Changed in deja-dup:
importance: Medium → Wishlist
Revision history for this message
exactt (giesbert) wrote :

as this option is only required upon creation of the bucket it would be useful to be able to either set the name of a pre-existing bucket or be asked upon creation of the bucket by deja dup.

looking forward to see either option implemented. thx for the great tool!

Revision history for this message
Craig Loftus (craigloftus) wrote :

Manually setting the bucket name to one you've created within AWS with the correct region seems to work fine and is a relatively simple hack. I was inspired by the answer to question 81409 [1], the required dconf command is below and more details were an excuse for a blog post [2].

$ dconf write /org/gnome/deja-dup/s3/bucket \'bucket-name\'


Revision history for this message
Robert Falkowitz (jcarberry) wrote :

Although this is an old thread, the issue still exists.
I can do a backup using deja-dup to a bucket created by deja-dup in the US East region.
However, I want the backup to be in a bucket I created previously in the Europe West region. If I change the bucket name as per Craig Loftus' remarks above, the backup fails with the following messages:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1532, in <module>
  File "/usr/bin/duplicity", line 1526, in with_tempdir
  File "/usr/bin/duplicity", line 1364, in main
    action = commandline.ProcessCommandLine(sys.argv[1:])
  File "/usr/lib/python2.7/dist-packages/duplicity/", line 1108, in ProcessCommandLine
    globals.backend = backend.get_backend(args[0])
  File "/usr/lib/python2.7/dist-packages/duplicity/", line 223, in get_backend
    obj = get_backend_object(url_string)
  File "/usr/lib/python2.7/dist-packages/duplicity/", line 209, in get_backend_object
    return factory(pu)
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/", line 161, in __init__
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/", line 187, in resetConnection
    if "NoSuchBucket" in e.error_code:
AttributeError: 'CertificateError' object has no attribute 'error_code'

And yet, that bucket exists and the credentials being used are for an account that has full rights to that bucket.

Revision history for this message
Saket Srivastava (sakbhav) wrote :

This patch should fix the certificate issue and add a field to configure S3 bucket. Basically replacing the url with s3://<s3 host>/<bucket>/<folder> instead of http+s3://<bucket>/<folder> works.

Revision history for this message
Saket Srivastava (sakbhav) wrote :
Changed in deja-dup:
assignee: nobody → Saket Srivastava (sakbhav)
assignee: Saket Srivastava (sakbhav) → nobody
Revision history for this message
Michael Terry (mterry) wrote :

Support for S3 has been removed, per our cloud policy that prefers consumer oriented cloud services. Duplicity can still be used directly to backup or restore your S3 files.

Changed in deja-dup:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.