To summarise: I run duck --list <s3 address here> and it prompts for the key and pass which are supplied, I confirm to save my details and those details are stored in ~/.duck/credentials successfully with perms 664 with .duck perms 775 both owned by my user and the credentials appear to have been written successfully into the credentials file. But when I run a similar operation (in this case exactly the same request to list the dir), it prompts me again having told me it can't find the credentials.
Listing directory path…
Login s3.amazonaws.com. Login s3.amazonaws.com – S3 with username and password. No login credentials could be found in the Keychain.
Access Key ID:
The text was updated successfully, but these errors were encountered:
However, I am able to specify credentials on the command line using the -u and -p options.
(side note, I tried using -i and also using -i and both forms result in: "Login s3.amazonaws.com. Login failed. The AWS Access Key Id you provided does not exist in our records." I presume I misunderstand what -i is intended for?)
The -i flag is intended for an SSH key, the kind you generate with the command ssh-keygen that gets saved to ~/.ssh/. We could make our lives easier by using the -u username/access key and -p password flags in the mean time.