You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CyberDuck doesn't support assume role functionalities of AWS.
So it means that accessKeyID and accessToken from centralised authentication
account can't be used to access a bucket in a different account.
AWS Sdks and aws cli for example support profiles nicely and more and more programs does it too.
ex:
awscli -profile "accountprod"
awscli -profile "accountperf"
Would be awesome if you could include this functionality, its actually part of AWS best practises.
Basically , one checkbox to activate profile, and if checked, a new textbox to specify the profile that are usually stored in .aws/credentials
CyberDuck doesn't support assume role functionalities of AWS.
So it means that accessKeyID and accessToken from centralised authentication
account can't be used to access a bucket in a different account.
AWS Sdks and aws cli for example support profiles nicely and more and more programs does it too.
ex:
awscli -profile "accountprod"
awscli -profile "accountperf"
Would be awesome if you could include this functionality, its actually part of AWS best practises.
Basically , one checkbox to activate profile, and if checked, a new textbox to specify the profile that are usually stored in
.aws/credentials
example:
Thanks a lot.
The text was updated successfully, but these errors were encountered: