• Resolved zpqrtbnk

    (@zpqrtbnk)


    Have tried both AWS S3 and Generic S3 and cannot get them to work. My bucket is named “foo” in region “eu-west-1” and is configured so that a tool such as CloudBerry Explorer can access it, and list and put and delete files, using the same keys I configure in UD.

    The s3:// style used by AWS S3 does not seem to support indicating a region. And thus, every attempt to access the bucket fails because of an endpoint error.

    The s3generic:// (?) style used by Generic S3 is same but Generic S3 also supports specifying an endpoint, which I set to “s3-eu-west-1.amazonaws.com”. Alas, that triggers a “[AuthorizationHeaderMalformed] The authorization header is malformed; the region ‘us-east-1’ is wrong; expecting ‘eu-west-1’)” error.

    From what I understand, AWS S3 cannot work outside whatever is the default AWS AZ. Which leaves me with Generic S3. Which I don’t understand. Can you help?

    • This topic was modified 1 year, 5 months ago by zpqrtbnk.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Hello,

    When attempting to connect using the Amazon S3 remote storage location, what is the exact error message?

    Thread Starter zpqrtbnk

    (@zpqrtbnk)

    Things about how I should use the right endpoint for the bucket. Cannot copy the exact message as I have moved to a different solution for now.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Cannot get S3 to work’ is closed to new replies.