Fix S3 object storage failing when endpoint is not specified
This reverts https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53326 since the endpoint created from the pre-signed URL is incorrect. For S3 virtual hostnames (e.g. `https://bucket.us-west-1.amazonaws.com`, the bucket name should be ignored, so the endpoint should be `https://us-west-1.amazonaws.com` in this case. This causes the wrong endpoint to be used (`https://bucket.bucket.us-west-1.amazonaws.com`). A workaround for AWS S3 users is to pass `endpoint: s3.amazonaws.com` as a config.
Showing
Please register or sign in to comment