ext_url construction fails for S3 buckets outside us-east-1

[Ojaybee]

When syncing media to an AWS S3 bucket located outside the us-east-1 region, the ext_url generated by media-sync defaults to the legacy global S3 format:

https://s3.amazonaws.com/{bucket}/{path}

This format only works for buckets in us-east-1. For buckets in other regions (e.g., eu-west-1), AWS returns AccessDenied when accessing this URL, even with correct public-read permissions and bucket policies.

Possible fix

If the region specified in config.yaml is not us-east-1 build the ext_url with https://{bucket}.s3.{config.minio.region}.amazonaws.com/{path}

Alternatively expose a config option like external_url_template for more flexibility in config.yaml

[tomasMizera]

Hi @Ojaybee, thanks for letting us know, we will investigate further!

[JanCaha]

@Ojaybee what is your endpoint configuration? It seems pretty fixable, but it would be good to know how exactly are setting this up

[Ojaybee]

Here's part of the config.yaml

minio: endpoint: s3.amazonaws.com access_key: <access key> secret_key: <secret-key> region: us-east-1 bucket: <my-bucket> secure: true

Is it just a caase of changing the endpoint? The object URL I'd want looks like this https://{bucket}.s3.{config.minio.region}.amazonaws.com/{path}

Currently the easiest fix is just to use a bucket in us-east-1.

[JanCaha]

@Ojaybee I tried to propose solution by constructing the url based on your template if region is set and endpoint contains amazonaws.

Could you give it a test from the PR #41 and let me know if it works as expected? Thanks