Support regional S3 access
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Déjà Dup |
Wishlist
|
Unassigned |
Bug Description
I like in the UK, and need to use the --s3-european-
summary: |
- Doesn't sync with my s3 instance + Support regional S3 access |
Changed in deja-dup: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Michael Terry (mterry) wrote : | #1 |
Changed in deja-dup: | |
importance: | Medium → Wishlist |
exactt (giesbert) wrote : | #2 |
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!
Craig Loftus (craigloftus) wrote : | #3 |
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/
[1] https:/
[2] http://
Robert Falkowitz (jcarberry) wrote : | #4 |
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/
with_
File "/usr/bin/
fn()
File "/usr/bin/
action = commandline.
File "/usr/lib/
globals.backend = backend.
File "/usr/lib/
obj = get_backend_
File "/usr/lib/
return factory(pu)
File "/usr/lib/
self.
File "/usr/lib/
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.
Saket Srivastava (sakbhav) wrote : | #5 |
This patch should fix the certificate issue and add a field to configure S3 bucket. Basically replacing the url with s3://<s3 host>/<
Saket Srivastava (sakbhav) wrote : | #6 |
Changed in deja-dup: | |
assignee: | nobody → Saket Srivastava (sakbhav) |
assignee: | Saket Srivastava (sakbhav) → nobody |
Michael Terry (mterry) wrote : | #7 |
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 |
There's now also an Asian (Singapore) region.