No pre-signed URLs available when using Credentials from AWS Command Line Interface connection profile

[foursec]

Hi Team,
Thanks for the great product.
Here is my question - I can successfully connect and perform S3 operations using Credentials from AWS Command Line Interface. However Pre-signed URL is missing from the list of actions in Edit → Copy URL→ Signed URL or File → Info
The docs say:

It is required that your AWS credentials are saved in keychain. Refer to Passwords.

Use keychain option is surely turned on.

I was digging around and didn't find a way to satisfy this requirement. Is there something I am missing here?

Thanks

Desktop (please complete the following information):

• macOS
• Version 8.4.4 (38366)

[dkocher]

This is expected with the current implementation as we cannot create signed URLs without a secret found in the password store (Keychain) ¹. With the Credentials from AWS Command Line Interface connection profile the secret key is not saved.

Footnotes

1. https://github.com/iterate-ch/cyberduck/blob/ce5193a616ea945b9c4b6785153ddfb551d860df/s3/src/main/java/ch/cyberduck/core/s3/S3UrlProvider.java#L179-L182 ↩

[foursec]

Thanks for info.
Does Amazon S3 connection profile with hardcoded aws_access_key_id and aws_secret_access_key work for generating pre-signed URLs on Windows platforms which as I understand do not have a Keychain?

[AliveDevil]

Windows platforms which as I understand do not have a Keychain?

Keychain refers to the general concept of a credential manager. On Windows this is managed through the Windows Credential Manager.

[dkocher]

Thanks for info. Does Amazon S3 connection profile with hardcoded aws_access_key_id and aws_secret_access_key work for generating pre-signed URLs on Windows platforms which as I understand do not have a Keychain?

Using the generic S3 connection profile this is supported and credentials will be saved in the password manager.