[Cyberduck-trac] [Cyberduck] #11041: Cannot use AWS regions other than us-east-1 for S3

[Cyberduck]

#11041: Cannot use AWS regions other than us-east-1 for S3
--------------------+------------------------
 Reporter:  Shu99   |         Owner:  dkocher
     Type:  defect  |        Status:  new
 Priority:  normal  |     Milestone:
Component:  s3      |       Version:  7.3.1
 Severity:  normal  |    Resolution:
 Keywords:          |  Architecture:
 Platform:          |
--------------------+------------------------

Comment (by Shu99):

 Thanks for the quick response! I was able to connect using the
 `bucketname.s3.amazonaws.com` server. Then I realized that even using
 `s3.amazonaws.com` as server results in connections being opened to the
 bucket's region (`us-west-2` in my case).

 I have two recommendations:
 * Endpoint locality behavior is worth noting on the Cyberduck/S3 page, as
 folks who're trying to optimize the performance of their transfers may be
 misled and think that their data is flowing to the endpoint specified in
 the `server` field.
 * The error message was very confusing when I used `s3.us-
 west-2.amazonaws.com`. Improving this error message will greatly improve
 customer experience in this scenario.

--
Ticket URL: <https://trac.cyberduck.io/ticket/11041#comment:3>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows