-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
Temporary tokens (credentials from AWS STS) do not work with AWS GovCloud S3 #10594
Comments
The auto configuration from |
Thanks for checking! I also want to mention that there are now 2 GovCloud regions with different endpoints:
|
Replying to [comment:4 yla]:
Thanks a lot! Two questions:
Thanks! |
A new snapshot build has now been published. Please comment on this ticket if the issue is resolved (or reopen) as we cannot fully test this ourselves. |
Replying to [comment:7 dkocher]:
Hi dkocher, I can help with the testing. Unfortunately I'm still having issues, but its looking better. This is what I'm doing: I'm using the following profile:
When adding the profile to cyberduck I setServer to s3-us-gov-west-1.amazonaws.com and Profile Name in ~/.aws/credentials to cyberduck. I then get new temporary credentials from AWS and put them in my ~/.aws/credentials file like this:
When I double click on the the shortcut in cyberduck I see Authenticating as cyberduck in the lower left corner with a spinning icon, but it never connects. If I try to close cyberduck it gets locked up and I have to force quit. Is there a way to enable debug logs? Thank you for all your help and prompt response! |
The error I can reproduce here is
|
Replying to [comment:11 dkocher]:
Great! The AWS GovCloud S3 login issues are fixed. I can now log in (using the configuration in the credentials file) and see the directory listing. Unfortunately I run into an error when trying to download files or directories. Since I get the same error using the normal access keys, I created a new ticket #10596. Thanks! |
The S3(Credentials from AWS Security Token Service) profile (https://svn.cyberduck.io/trunk/profiles/S3%20(Credentials%20from%20AWS%20Security%20Token%20Service).cyberduckprofile) does not work with AWS GovCloud accounts. Cyberduck gets into a loop where it says "Authenticating as publish_profile" followed by "Login failed". I also tried using the AWS GovCloud profile (https://svn.cyberduck.io/trunk/profiles/S3%20Gov%20Cloud.cyberduckprofile), but it doesn't support temporary tokens. I also tried creating my own profile merging 'S3(Credentials from AWS Security Token Service)* and *AWS GovCloud'' but that didn't work either. Here is the custom profile I tried out:
This is the AWS credentials file I'm using:
Is there a way to support both AWS GovCloud and S3 (Credentials from AWS Security Token Service) at the same time?
Thanks!
The text was updated successfully, but these errors were encountered: