[Cyberduck-trac] [Cyberduck] #11757: Unable to connect to S3 Bucket

[Cyberduck]

#11757: Unable to connect to S3 Bucket
--------------------------------+-----------------------------------
 Reporter:  DarkDataConsulting  |         Owner:  DarkDataConsulting
     Type:  defect              |        Status:  reopened
 Priority:  normal              |     Milestone:
Component:  s3                  |       Version:  7.9.2
 Severity:  normal              |    Resolution:
 Keywords:                      |  Architecture:  Intel
 Platform:  Windows 10          |
--------------------------------+-----------------------------------
Changes (by DarkDataConsulting):

 * status:  closed => reopened
 * resolution:  worksforme =>


Comment:

 Replying to [comment:3 dkocher]:  Thank you for your response.  I have
 tried this and it will work only if I grant viewallmybuckets action in the
 user policy.  I have a requirement that users not be able to see any other
 bucket other than thier own.  Is this policy action required for Mountain
 Duck to connect?
 > You can connect to a specific bucket by specifying it in the _Path_
 setting in the bookmark. Do not alter the default hostname
 `s3.amazonaws.com`. The above URL is from the S3 console web application
 from AWS and not a valid S3 API URL.

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