problem using other regions for aws s3 storage

[kristjanvalur]

Steps to reproduce

1. Create aws bucket in, e.g. eu-west-1 (ireland). Set up access controls etc.
2. add external storage, giving bucket name and region
3. mount external storage
4. create text file in mounted storage

Expected behaviour

Text file appears

Actual behaviour

Error occurs. Log file includes a line with error from aws: ""

Server configuration

Operating system: CentOS 7

Web server: Apache

Database: PostgreSQL

ownCloud version: 10.0.10.4

S3 Object Storage version: 1.0.3

Workaround:

Explicitly supply the hostname: "s3.eu-west-1.amazonaws.com"
Do not supply a "region" in the region field.

Discussion:

It would appear that the paths being created for buckets outside the standard US region do not follow the recommended practice by amazon. See here for proper access using both virtual host addressing and path-style: https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro

• In a virtual-hosted–style URL, the bucket name is part of the domain name in the URL. For example:
  • http://bucket.s3.aws-region.amazonaws.com
  • http://bucket.s3.amazonaws.com
• In a path-style URL, the bucket name is not part of the domain. For example:
  • Region-specific endpoint, http://s3.aws-region.amazonaws.com/bucket
  • US East (N. Virginia) Region endpoint, http://s3.amazonaws.com/bucket

Using buckets in regions local to the server greatly speeds up access.

[caldetas]

Same Problem here, had to slightly adapt your workaround to get the S3 working with owncloud..

Workaround:

Explicitly supply the hostname: "s3.eu-west-1.amazonaws.com"
Region: "eu-west-1"

[kristjanvalur]

Astonishing that this is still a problem. The world is big.

[chenhaibiao280555]

Thanks for the workaroud solution! I have been stuck for days! I am using the docker version.