Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support me-south-1 region #10790

Closed
cyberduck opened this issue Sep 2, 2019 · 6 comments
Closed

Support me-south-1 region #10790

cyberduck opened this issue Sep 2, 2019 · 6 comments
Assignees
Labels
feature fixed s3
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Sep 2, 2019

540d0bd created the issue

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.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Sep 2, 2019

@dkocher commented

In 11d6240.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 29, 2020

@dkocher commented

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. 

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 1, 2020

@dkocher commented

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.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 1, 2020

@dkocher commented

Will be fixed in conjunction with #11036.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 4, 2020

@ylangisc commented

In 3ad40a2.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 30, 2020

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature fixed s3
Projects
None yet
Development

No branches or pull requests

2 participants