Cyberduck Mountain Duck CLI

Version 94 (modified by dkocher, on Dec 1, 2010 at 11:21:56 PM) (diff)

--

Cyberduck Help / Howto / Amazon S3

Transfer files to your S3 account and browse the S3 buckets and files in a hierarchical way. For a short overview of Amazon S3, refer to the Wikipedia article.

Connecting to Amazon S3

You must obtain the login credentials (Access Key ID and Secret Access Key) of your Amazon Web Services Account from the AWS Access Identifiers page. In the login prompt of Cyberduck upon connecting to S3 you enter the Access Key ID for the username and Secret Access Key for the password.

External buckets

Connecting to a bucket you are not the owner (and therefore not listed when logging in as above) is possible. You can access buckets owned by someone else if the ACL allows you to access it. Specify the bucket you want to access in the hostname to connect to like <bucketname>.s3.amazonaws.com. Your own buckets will not be displayed but only the third party bucket.

Third-Party S3 providers

There are several third parties beside Amazon offering S3 compatible cloud storage software or solutions.

Use S3 without SSL

It is discouraged to enable this option to connect plaintext to Amazon S3.

If you have a S3 implementation in your local network and can't connect using SSL, you can enable a hidden configuration option to connect using HTTP only without transport layer security.

defaults write ch.sudo.cyberduck protocol.s3.enable true

You will then have the added option S3/HTTP (Amazon Simple Storage Service) in the protocol dropdown selection in the Connection and Bookmark panels.

Storage Class

You have the option to store files using the Reduced Redundancy Storage (RRS) to reduce costs by storing non-critical, reproducible data at lower levels of redundancy. Set the default storage class in Preferences → S3 and edit the storage class for already uploaded files using File → Info → S3.

Buckets

To create a new bucket for your account, browse to the root and choose File → New Folder.... You can choose the bucket location in Preferences → S3. Note that Amazon has a different pricing scheme for different locations. Once created, you cannot change the location of a bucket. Supported locations are:

  • EU (Ireland)
  • US Standard
  • US-West (Northern California)
  • Asia Pacific (Singapore)

Important: Because the bucket name must be globally unique the operation might fail if the name is already taken by someone else (E.g. don't assume any common name like media or images will be available).

Bucket Access Logging

When this option is enabled in the File → Info panel of a bucket or any file within, available log records for this bucket are periodically aggregated into log files and delivered to <bucketname>/logs.

To toggle CloudFront access logging, select the the Distribution panel in the File → Info window.

Folders

Creating a folder inside a bucket will create a placeholder object named after the directory, has no data content and the mimetype application/x-directory.

Supported thirdparty folder placeholder formats

Access Control (ACL)

Amazon S3 uses Access Control List (ACL) settings to control who may access or modify items stored in S3. By default, all buckets and objects created in S3 are accessible only to the account owner. You can edit ACLs in File → Info → Permissions.

Canonical User ID Grantee

If you enter a user ID unknown to AWS, the error message S3 Error Message. Bad Request. Invalid id. will be displayed.

Email Address Grantee

If you enter an email address unknown to AWS, the error message S3 Error Message. Bad Request. Invalid id. will be displayed. If multiple accounts are registered with AWS for the given email address, the error message Bad Request. The e-mail address you provided is associated with more than one account. Please retry your request using a different identification method or after resolving the ambiguity. is returned.

All Users Group Grantee

You must give the group grantee http://acs.amazonaws.com/groups/global/AllUsers read permissions for your objects to make them accessible using a regular web browser for everyone.

If bucket logging is enabled, the bucket ACL will have READ_ACP and WRITE permissions for the group grantee http://acs.amazonaws.com/groups/s3/LogDelivery.

Default ACLs

For new files uploaded, the ACL applied depends on the setting in Preferences → Transfers → Permissions → Uploads. If you want files uploaded accessible to anyone in the browser, make sure to set the following:

  • If you have selected to apply the permissions of the local file or folder for uploads, then check the access permissions of the file in

Finder.app. If everyone is allowed read access in the Sharing & Permissions section of the Finder.app Info window, the file should have a READ ACL in S3 for http://acs.amazonaws.com/groups/global/AllUsers.

  • If you have choosen to set default permissions for uploads, make sure Read access for Others is selected in the Upload Permissions Transfer Preferences.

Versions

Versioning can be enabled per bucket in File → Info → S3. You can view all revisions of a file in the browser by choosing View → Show Hidden Files.

Revert

To revert to a previous version and make it the current, choose File → Revert.

Multi-Factor Authentication (MFA) Delete

To enable Multi-Factor Authentication (MFA) Delete, you need to purchase a compatible authentication device. Toggle MFA in File → Info → S3. When enabled, you are prompted for the device number and one-time token in a login prompt. Never reenter a token in the prompt already used before. A token is only valid for a single request. Wait for the previous token to disapear from the device screen and request a new token from the device.

Public URLs

You can access all URLs (including from CDN configurations) from the menu Edit → Copy URL and File → Open URL.

Signed temporary URLs

Copy the signed URL from File → Info → S3. Public access to the URL is granted for 24 hours by default.

  • Choose the lifetime for publicly available auto-expiring signed URL using the hidden option s3.url.expire.seconds.
defaults write ch.sudo.cyberduck s3.url.expire.seconds 86400

BitTorrent URLs

Use File → Info → S3 to copy the BitTorrent URL of a selected file. The ACL of the object must allow aonymous read. One important thing to note is that the .torrent file describing an Amazon S3 object is generated on-demand, the first time the Torrent URL is requested. Generating the .torrent for an object takes time proportional to the size of that object. For large objects, this time can be significant. Therefore, before publishing a ?torrent link, we suggest making the first request for it yourself. Amazon S3 might take several minutes to respond to this first request, as it generates the .torrent file. Unless you update the object in question, subsequent requests for the .torrent will be fast.

Metadata

You can edit standard HTTP headers and add custom HTTP headers to files to store metadata. Choose File → Info → S3 to edit headers.

Refer to the Info panel wiki page.

Default metadata

Currently only possible using a hidden configuration option you can define default headers to be added for uploads. Multiple headers must be separated using a whitespace delimiter. Key and value of a header are seperated with =. For example if you want to add a HTTP header for Cache-Control and one named Creator you would set

defaults write ch.sudo.cyberduck s3.metadata.default "Cache-Control=public,max-age=86400 Creator=Cyberduck"

Cache Control Setting

This option lets you control how long a client accessing objects from your S3 bucket will cache the content and thus lowering the number of access to your S3 storage. In conjunction with Amazon CloudFront, it controls the time an object stays in an edge location until it expires. After the object expires, CloudFront must go back to the origin server the next time that edge location needs to serve that object. By default, all objects automatically expire after 24 hours when no custom Cache-Control header is set.

The default setting is Cache-Control: public,max-age=2052000 when choosing to add a custom Cache-Control header in the Info panel which translates to a cache expiration of one month (one month in seconds equals more or less 60*60*24*30).

defaults write ch.sudo.cyberduck s3.cache.seconds 2052000

Tip: Use curl -I <http://<bucketname>.s3.amazonaws.com/<key> to debug HTTP headers.

Distribution (CDN)

Refer to Amazon CloudFront distribution.

Problems

SSL certificate trust verification

When listing a bucket that has a . in its name, connecting will give a trust verification failure The certificate is not valid (host name mismatch) for the wildcard certificate *.s3.amazonaws.com. Because the wildcard only applies to one level in the domain name, you must manually trust this certificate.

References

swiss made software