[Cyberduck-trac] [Cyberduck] #11029: The AWS Access Key Id provided doesnot exist in our records

[Cyberduck]

#11029: The AWS Access Key Id provided doesnot exist in our records
------------------------+----------------------
 Reporter:  avirup      |         Owner:
     Type:  defect      |        Status:  new
 Priority:  highest     |     Milestone:
Component:  s3          |       Version:  7.3.0
 Severity:  blocker     |    Resolution:
 Keywords:              |  Architecture:
 Platform:  Windows 10  |
------------------------+----------------------

Comment (by avirup):

 Thanks for your reply.

 I have selected ''S3 (Credentials from AWS Security Token Service)'' in
 the bookmark protocol selection and was able to connect successfully. I
 have configured a "testuser" profile under
 "%UserProfile%/.aws/credentials"

 Below is the configuration i have used.

 [testuser]
 aws_access_key_id = *****************
 aws_secret_access_key = *****************
 aws_session_token = ******************************************
 [testrole]
 role_arn = [Role ARN]
 source_profile = testuser

 Is this correct?
 Also would like to know is there a way to configure Cyberduck to read aws
 credentials file from another location instead of "C" drive.
 Also is there a way to configure the role from the credential file instead
 of setting the role from IAM?

--
Ticket URL: <https://trac.cyberduck.io/ticket/11029#comment:2>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows