Cyberduck Mountain Duck CLI

#9992 closed feature (duplicate)

CyberDuck to support AWS profiles

Reported by: raccoon Owned by:
Priority: normal Milestone:
Component: s3 Version: 6.0.1
Severity: normal Keywords:
Cc: Architecture: Intel
Platform:

Description (last modified by raccoon)

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:

[default]
aws_access_key_id = AKIA....
aws_secret_access_key = 

[profileprod]
region=us-east-1
role_arn=arn:aws:iam::1234567890:role/cross-account-access
source_profile=default

[profileperf]
region=us-east-1
role_arn=arn:aws:iam::0987654321:role/cross-account-access
source_profile=default

[profiletest]
region=us-east-1
role_arn=arn:aws:iam::010203040506:role/cross-account-access
source_profile=default

Thanks a lot.

Change History (2)

comment:1 Changed on Jun 27, 2017 at 11:05:11 AM by raccoon

  • Description modified (diff)

comment:2 Changed on Jun 27, 2017 at 3:28:21 PM by dkocher

  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate for #8880.

Note: See TracTickets for help on using tickets.
swiss made software