Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The AWS Access Key Id provided doesnot exist in our records #11029

Closed
cyberduck opened this issue Apr 19, 2020 · 3 comments
Closed

The AWS Access Key Id provided doesnot exist in our records #11029

cyberduck opened this issue Apr 19, 2020 · 3 comments
Labels
bug s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

b4b02e0 created the issue

I am trying to access s3 bucket using the S3(Credentials from AWS Security Token Service Profile).
I am generating temporary Access Key ID and Secret Access Key using AWS STS.
I am using Amazon S3 profile

But getting the below error:
The AWS Access Key Id provided doesnot exist in our records. Please contact your web hosting service provider for assistance.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Make sure to select S3 (Credentials from AWS Security Token Service) in the bookmark protocol selection.

@cyberduck
Copy link
Collaborator Author

b4b02e0 commented

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?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please refer to our documentation.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck