Aws s3 EU(Paris)

Getting Help
1

Hello,

On a new S3 bucket, created form the S3 console at EU(Paris) region.
Using an IAM user created with full access to S3. AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY correctly setted.

using “init” result in a error :

restic -r s3:s3.amazonaws.com/kw-bkp-sql-local init

create backend at s3:s3.amazonaws.com/kw-bkp-sql-local failed: client.BucketExists: Access Denied.

Running init on a inexistent bucket is ok (bucket created by restic at USA Est):

restic -r s3:s3.amazonaws.com/kw-bkp-sql-local2 init

enter password for new backend:
enter password again:
created restic backend 7737dd7d26 at s3:s3.amazonaws.com/kw-bkp-sql-local2

Running “init” in a existing bucket not located in UE(Paris) is Ok (UE (Francfort))

Is there a problem with the UE(Paris) Region ?

Thanks
David

2

Hm, I’m not aware of any issue with specific zones in S3. Is the user account you’re using to access S3 restricted in any way?

Which restic version is that? Did you try with 0.8.1?

3

I’m using Restic lastest version:

~# restic version
restic 0.8.1
compiled with go1.9.2 on linux/amd64

The IAM User credentials I use are the same in both case (Paris or other region). Wildcard authorization on every S3 buckets/objects

I’ve created two fresh buckets, one in Francfort, another one in Paris. Here are the output of the two “init” command :

~# restic -r s3:s3.amazonaws.com/restic-test-francfort init
enter password for new backend:
enter password again:
created restic backend b805b82192 at s3:s3.amazonaws.com/restic-test-francfort

Please note that knowledge of your password is required to access
the repository. Losing your password means that your data is
irrecoverably lost.

~# restic -r s3:s3.amazonaws.com/restic-test-paris init
create backend at s3:s3.amazonaws.com/restic-test-paris failed: client.BucketExists: Access Denied.
4

Ah, it looks like the eu-west-3 zone has only been added two days ago to minio-go (which is the library we’re using in restic to access s3):

So we’ll need to wait until minio-go does its next release, then update our dependencies and build new binaries.

If you don’t want to wait so long, you can try the following patch, I’ve verified that it works then:

Then you need to compile restic from source, by running go run build.go. Afterwards you should be able to use the eu-west-3 zone.

5

Very good news, thanks for your time investigating this.

6

Let me know if you try the patch please :slight_smile:

7

Sorry, no. I don’t have a env ready to compile Go.
But if you can give me a x64 linux binary, I can easily test S3 in EU(Paris) region

8

Here you go: https://fd0.me/tmp/restic_v0.8.1-35-g5723636b-dirty_linux_amd64.bz2

9

Works as expected :slight_smile:

 ~# ./restic_v0.8.1-35-g5723636b-dirty_linux_amd64 init
created restic backend 6871c7ea3f at s3:s3.amazonaws.com/restic-test-paris

Please note that knowledge of your password is required to access
the repository. Losing your password means that your data is
irrecoverably lost.



~# ./restic_v0.8.1-35-g5723636b-dirty_linux_amd64 backup ./test
password is correct
scan [/root/test]
scanned 1 directories, 2 files in 0:00
[0:00] 100.00%  0B/s  18B / 18B  3 / 3 items  0 errors  ETA 0:00
duration: 0:00, 0.00MiB/s
snapshot f6e1e83e saved
10

Great, thanks for the feedback!

The folks at Minio have released a new version of minio-go, which supports the eu-west-3 zone. I’ve created a pull request which will update the dependencies for restic