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
Is your feature request related to a problem? Please describe.
There's no documentation on how to use cyberduck with AWS IAM Identity Center.
Describe the solution you'd like
Documentation for said feature.
Describe alternatives you've considered
Bumbling around until you figure out how to do it yourself. By default Cyberduck assumes you just have a access key id and secret, so it took me a bit to figure this out.
Additional context
I wrote up some documentation for it:
Using Cyberduck with AWS IAM Identity Center
Go to settings → Profiles. Select S3 (Credentials from AWS Command Line Interface). Your setting will automatically be saved, so you can close the window.
Next, download the AWS cli. Then, go to AWS IAM Identity Center and click on "Command line or programmatic access" for the account you want to access. Follow the instructions.
Try running aws s3 ls --profile=<profile>, replacing <profile> with your profile name. If you get results, you are good to continue.
Now, back to Cyberduck. Click on open connection and choose S3 (Credentials from AWS Command Line Interface). Type in your profile name and click connect. Now you should be able to see your buckets!
The text was updated successfully, but these errors were encountered:
dkocher
changed the title
[documentation] Please document process for using Cyberduck with AWS IAM Identity Center
Document process for using Cyberduck with AWS IAM Identity Center
Sep 1, 2023
Is your feature request related to a problem? Please describe.
There's no documentation on how to use cyberduck with AWS IAM Identity Center.
Describe the solution you'd like
Documentation for said feature.
Describe alternatives you've considered
Bumbling around until you figure out how to do it yourself. By default Cyberduck assumes you just have a access key id and secret, so it took me a bit to figure this out.
Additional context
I wrote up some documentation for it:
Using Cyberduck with AWS IAM Identity Center
Go to settings → Profiles. Select
S3 (Credentials from AWS Command Line Interface)
. Your setting will automatically be saved, so you can close the window.Next, download the AWS cli. Then, go to AWS IAM Identity Center and click on "Command line or programmatic access" for the account you want to access. Follow the instructions.
Try running
aws s3 ls --profile=<profile>
, replacing <profile> with your profile name. If you get results, you are good to continue.Now, back to Cyberduck. Click on open connection and choose S3 (Credentials from AWS Command Line Interface). Type in your profile name and click connect. Now you should be able to see your buckets!
The text was updated successfully, but these errors were encountered: