Repository navigation
How do I access AWS S3 using aws_access_key_id, aws_secretaccess_key and an aws_session token with Cyberduck #18668
Replies: 4 comments
|
Just had some random progress ... found an old closed issue saying this profile had been deleted as the same as "S3 (Credentials from AWS Command Line Interface).cyberduckprofile" - treid that - but it just hung / ignored when I clicked connect anyway - for reasons unknown I tried to create a bookmark (rather than quick connect) and that has worked ... so not sure why - but that seems to be the work around - will update as I find out more |
|
Love chatting with myself - sorry for wasting the bytes - but for anyone else finding this ... the combination of setting Token Configurable true (in the old "S3 (Credentials from AWS Security Token Service).cyberduckprofile" ( which then made it the same as the current "S3 (Credentials from AWS Command Line Interface).cyberduckprofile" ) and then also creating a bookmark - rather than just using the one off connect dialog was enough to make this work |
|
@dkocher - I believe I now have found an issue which is although this profile works with latest ( > 9.2.4 - 9.6.0 ) if used with a bookmark, it does not seem to work using the "Open Connection" dialog - which seems to hang / ignore on clicking connect. Can you convert this back into an Issue, would you prefer I open a new Issue ... or should I just go :-) |
|
The "S3 (Credentials from AWS Security Token Service)" profile was removed. The S3 (Credentials from AWS Command Line Interface) profile replaces it. It reads Enter the profile name (here Connecting through a bookmark is the recommended way and works as expected, as you found. The Open Connection dialog hanging or ignoring a click on Connect with the "S3 (Credentials from AWS Command Line Interface)" profile should not happen, though. Before we treat this as a bug, please post the following here:
If the log confirms a bug, we will convert this discussion to an issue accordingly. Sidenote: Please make sure to attach the log files through the GitHub web interface, as they won't be visible to us otherwise. |
Uh oh!
There was an error while loading. Please reload this page.
I used to be able to access S3 using a profile called "S3 (Credentials from AWS Security Token Service)" which I presume I downloaded form here ?
I think I probably originally found via this page : https://blog.cyberduck.io/2018/08/07/connecting-using-assumerole-from-aws-security-token-service-sts/
FWIW - this still works for me up to and including cyberduck 9.2.4 ...
after that it stop working. I tried making a change to the profile to set token configurable true ( as mentioned here : #18248 ) but think that is a slightly different issue
I note the "S3 (Credentials from AWS Security Token Service)." doesn't seem to exist any more - I have attached a zipped copy.
S3 (Credentials from AWS Security Token Service).cyberduckprofile.zip
I am at a bit of a loss - I have looked at the various AWS S3 CLI and AWS STS profiles - but non of them see to play ball.
As I say it still works with cyberduck prior to and including 9.2.4 - so its not an AWS change
Please can anyone help with this - as I am at a total loss
All reactions