Regions other than us-east-1 are broken

[wpuckering]

It seems like setting a different region other than us-east-1 does not work properly. I have a bucket in ca-central-1 which I can upload and delete files from just fine, but I can't edit a text file once uploaded to the bucket. I get the following error saying that the region is invalid:

A snippet of my configuration file showing that I have set my region to ca-central-1 is below:

Seems like this piece of code is the culprit:

[mickael-kerjean]

Thanks for the report!
I'll try to fix somewhere next week.

[mickael-kerjean]

I wasn't able to replicate your error with a bucket in Canada. I'm not sure where did you get the full endpoint url from, can you try this:

    "connections": [
        {
            "type": "s3",
            "label": "S3",
            "access_key_id": "xxxxxxx",
            "secret_access_key": "xxxxxxx",
            "region": "ca-central-1",
            "advanced": false,
            "encryption_key": "",
            "endpoint": "",
            "path": "/your_canadian_bucket_name/"
        }
    ]

[mickael-kerjean]

Looks like problem solve in here. I'm closing but feel free to comment back and I'll reopen

[stefanoCaroli]

Hi, I'm trying to connect to a bucket in Europe (region: eu-west-1) but I am still experiencing the same error code:

Am I missing something in the configuration or is it just the same bug mentioned above?

[gianlucapisati]

Hi @mickael-kerjean same problem here, buckets different than us-east-1 seems not to be working

my connection string is like this:

"connections": [
        {
            "type": "s3",
            "label": "S3",
            "access_key_id": "xxxxxxx",
            "secret_access_key": "xxxxxxx",
            "region": "eu-west-1",
            "advanced": false,
            "encryption_key": "",
            "endpoint": "",
            "path": ""
        }
    ]

if i don't specify any path it loads the initial list of buckets, but then, when I open one bucket I receive the same error of @stefanoCaroli and @wpuckering

[mickael-kerjean]

Can someone send me a testing account from which I can try?

[mickael-kerjean]

I haven't received anything at all. I'm closing until there's enough information to act upon.

[TetrisBlack]

Hello,
I have the same issue with the region s3 bucket config. I wanted to test my assumption, but I couldn't get the backend to build on my machine, but could attach a debugger. Nevertheless, I think the problem lies in this line:

filestash/server/plugin/plg_backend_s3/index.go

Line 439 in 625e0ed

res, err := s.client.GetBucketLocation(&s3.GetBucketLocationInput{

It always results in an error. And overwriting the region.
Something similar was discussed in here -> aws/aws-sdk-go#720.

EDIT:
If you add "s3:GetBucketLocation" to your allowed actions. It works as well. Maybe add a list of minimum needed S3 Permissions?

[jonasjancarik]

EDIT: If you add "s3:GetBucketLocation" to your allowed actions. It works as well. Maybe add a list of minimum needed S3 Permissions?

I second that, adding "s3:GetBucketLocation" to allowed actions also fixed the issue for us.

[mickael-kerjean]

I still need a testing account to test this out, can you send one? email is in my profile

[jonasjancarik]

Do you mean an access key/secret key? I can't use our corporate one (for obvious reasons) but I'll try to sign up for a new AWS account at some point soon to teset this.