Cyberduck Mountain Duck CLI

Changes between Version 262 and Version 263 of help/en/howto/s3


Ignore:
Timestamp:
Mar 9, 2019 9:21:08 PM (2 years ago)
Author:
dkocher
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • help/en/howto/s3

    v262 v263  
    5959
    6060that will fetch temporary credentials from EC2 instance metadata service at `http://169.254.169.254/latest/meta-data/iam/security-credentials/s3access` to authenticate. Edit the profile to change the role name `s3access` to match your IAM configuration.
     61
     62=== Connecting using credentials in ~/.aws/credentials  ===
     63Instead of providing Access Key ID and Secret Access Key, authenticate using credentials managed in `~/aws/credentials` using third party tools.
     64
     65 * [https://svn.cyberduck.io/trunk/profiles/S3%20(Credentials%20from%20AWS%20Command%20Line%20Interface).cyberduckprofile Download] the ''S3 (Credentials from AWS Security Token Service)'' profile for preconfigured settings. You must provide configuration in the standard credentials property file `~/.aws/credentials` from [https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html AWS Command Line Interface]. Configure a bookmark with the field titled ''Profile Name in ~/.aws/credentials'' matching the profile name from `~/.aws/credentials`. The properties `aws_access_key_id`, `aws_secret_access_key` and `aws_session_token` are supported.
     66
     67You might be interested in scripts maintained by third parties to facility managing credentials
     68 * [https://github.com/jmvbxx/cyberduck-s3-config Manage configuration files for Cyberduck S3 (AssumeRoles from AWS STS)]
     69 * [https://github.com/vwal/awscli-mfa Utilities for easy management of AWS MFA and role sessions and virtual MFA devices]
    6170
    6271=== Connecting using AssumeRole from AWS Security Token Service (STS) ===
     
    7887   mfa_serial=arn:aws:iam::123456789012:mfa/testuser
    7988}}}
    80 
    81 === Connecting using credentials managed in ~/.aws/credentials  ===
    82 Instead of providing Access Key ID and Secret Access Key, authenticate using credentials managed in `~/aws/credentials` using third party tools. The properties `aws_access_key_id`, `aws_secret_access_key` and `aws_session_token` are supported. Configure a bookmark with the field titled ''Profile Name in ~/.aws/credentials'' matching the profile name from `~/.aws/credentials`.
    83 
    84 You might be interested in scripts maintained by third parties to facility managing credentials
    85  * [https://github.com/jmvbxx/cyberduck-s3-config Manage configuration files for Cyberduck S3 (AssumeRoles from AWS STS)]
    86  * [https://github.com/vwal/awscli-mfa Utilities for easy management of AWS MFA and role sessions and virtual MFA devices]
    8789
    8890=== Read credentials from ~/.aws/credentials ===