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

Can't connect to a client's S3 server #11072

Closed
cyberduck opened this issue Jun 16, 2020 · 1 comment
Closed

Can't connect to a client's S3 server #11072

cyberduck opened this issue Jun 16, 2020 · 1 comment
Labels
bug high priority s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

0f76597 created the issue

Hello,

A client has asked me to use their Amazon S3 credentials to get files off their server, however they require that I also use a specific "bucket name" to connect correctly.

My client shared a screenshot of their cyberduck UI (version 7.3.1) that has extra options at the bottom of their "Open Connection" window. The three options in the extra options are: 1) Path, 2) Connect Mode, and 3) Encoding.

The Path option is where I should put their Bucket Name, however I do not have those options in my client. There is no "extra options" at the bottom of my Open Connection window. The last option in my Open Connection window is "add to keychain".

My question is, how do I input a Bucket Name or Path so I can connect to my client's server? I have the access Key ID and Secret Access Key, but that's not enough to connect.

Thanks!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Create a bookmark instead which has the additional options.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug high priority s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

1 participant