You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Duck (the command line tool) doesn't have support for S3 region me-south-1. I noticed that a previous support ticket was opened for Cyberduck and there are nightly/snapshot builds for Cyberduck 7.1 .
However, there seems to be none for duck 7.1 to be run on Windows. Also, I couldn't find any instructions on how to build a nightly/snapshot of the latest duck to be run on Windows.
The text was updated successfully, but these errors were encountered:
There is currently an issue accessing recently announced regions me-south-1, eu-south-1, af-south-1 that requires an update to our handling of Virtual Hosted-Style Requests to include the region.
The eu-south-1 location constraint is incompatible for the region specific endpoint this request was sent to.
The legacy global endpoint is also used for virtual hosted-style requests in other supported Regions. If you create a bucket in a Region that was launched before March 20, 2019 and use the legacy global endpoint, Amazon S3 updates the DNS to reroute the request to the correct location, which might take time. In the meantime, the default rule applies, and your virtual hosted–style request goes to the US East (N. Virginia) Region. Amazon S3 then redirects it with an HTTP 307 redirect to the correct Region. For S3 buckets in Regions launched after March 20, 2019, the DNS doesn't route your request directly to the AWS Region where your bucket resides. It returns an HTTP 400 Bad Request error instead. For more information, see Request redirection and the REST API.
Hello,
Duck (the command line tool) doesn't have support for S3 region me-south-1. I noticed that a previous support ticket was opened for Cyberduck and there are nightly/snapshot builds for Cyberduck 7.1 .
However, there seems to be none for duck 7.1 to be run on Windows. Also, I couldn't find any instructions on how to build a nightly/snapshot of the latest duck to be run on Windows.
The text was updated successfully, but these errors were encountered: