Drag and drop a zipped File Geodatabase or Shapefile into Cyberduck or click the “Upload” button, and choose the zipped dataset.Open Cyberduck, choose the connection you configured in the last step, and click “Connect”.With your connection to S3 now established you can upload your dataset for the first time. Your AWS S3 connection details are the same for every dataset you’ll be publishing – so you’ll only need to setup a single Cyberduck connection for all of your datasets. You’ve now successfully configured Cyberduck for the first time. If successful, you should see this screen. Click “Connect” and Cyberduck will attempt to connect to your S3 folder.Secret Access Key to the field of the same name.S3 Access Key to the Access Key ID field.In Cyberduck, choose S3 (Amazon Simple Storage Service) from the connection type menu and add your:.In the Data Upload Tool, navigate to the Upload tab on your dataset to find your AWS S3 credentials.Open Cyberduck and choose “Open Connection”.This is ideal choice for uploading larger datasets (in excess of 2GB) or where being able to resume an upload is important (for example, if you have a slow or unreliable internet connection). I'm supporting Cyberduck users that have limited text editor / terminal experience, so a workflow that relies on them making changes to ~/.aws/credentials to update their access keys / session token is cumbersome.Cyberduck is a desktop file transfer application that supports FTP, AWS S3, Dropbox, and other file storage solutions. There's an open issue for support in the aws java v1 sdk, but I'm not sure if it will be implemented. This is a screenshot of the AWS SSO login page that presents temporary credentials and how to use them.Īnother option would be to upgrade to aws java sdk v2 which supports the SSO credentials provider.

Cyberduck has worked great with the user/role auth, and I have a couple feature requests that I think would allow it to work with AWS SSO.įor an Amazon S3 connection, add a field to enter an AWS Session Token directly, along with the access key id and secret access key.ĪWS SSO presents a nice copy/paste window for session credentials, and it would be easy for a user to copy/paste the values from 'Option 3' (below) into Cyberduck when connecting. I'm in the process of migrating from AWS IAM user / AssumeRole authentication to using the AWS Single Sign-On service.

Cyberduck amazon s3 setup