Enable to add to Add AWS session token while trying to connect with amazon s3

[Moeez-nclouds]

Hi everyone,
I hope this message finds you well.

I am currently attempting to establish a connection with Amazon S3 using Cyberduck while utilizing temporary AWS credentials. However, I have encountered an obstacle as I cannot locate the designated field to input the AWS session token. According to some resources, the Session Token field in Cyberduck might not be readily visible by default. To make it visible, one is advised to navigate to Preferences > Connections > Amazon S3 and select the option to Show Session Token. Nevertheless, I have followed these instructions diligently, yet the checkbox remains elusive. I would sincerely appreciate any assistance or guidance you can provide on this matter.
Thank you

[dkocher]

There is support connecting to S3 with temporary credentials including a session token by using dedicated connection profiles.

• Connecting with Temporary Access Credentials (Token) from EC2
• Connecting Using Credentials from AWS Command Line Interface
• Connecting Using AssumeRole from AWS Security Token Service (STS)- AWS Single Sign-On

There is work in progress ¹ to facilitate the setup of connections using AssumeRole APIs of STS in particular when used with an identity provider (OAuth).

Footnotes

1. Suport to login using temporary credentials from Security Token Service (STS API) using OpenID Connect web identity #13804 ↩

[Moeez-nclouds]

Hi @dkocher ,
I hope you are well,
Thank you for your response, I tried to download the profile form the links that you mentioned but i'm getting this error. Can you please guide me regarding this,
Thanks

[Xarno]

That is not an error. You need to save this XML file. Your Browser thought it could be helpful by showing you the contents, but you need the file „someName.cyberduckprofile“ on your harddrive. Then doubleclick it.

[dkocher]

Currently because of a regression ¹ the profiles are not working as expected in the current release 8.6.2.

Footnotes

1. Failure configuring credentials from AWS CLI setup #14970 ↩