Cyberduck Mountain Duck CLI

Changes between Version 80 and Version 81 of help/en/howto/s3


Ignore:
Timestamp:
Sep 9, 2010 1:14:23 PM (11 years ago)
Author:
dkocher
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • help/en/howto/s3

    v80 v81  
    5656Creating a folder inside a bucket will create a placeholder object named after the directory, has no data content and the mimetype `application/x-directory`.
    5757
    58 == Files ==
    59 
    60 === Access Control (ACL) ===
     58== Access Control (ACL) ==
    6159Amazon 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''.
    6260
    6361[[Image(acl.png)]]
    6462
    65 ==== Canonical User ID Grantee ====
     63=== Canonical User ID Grantee ===
    6664If you enter a user ID unknown to AWS, the error message `S3 Error Message. Bad Request. Invalid id.` will be displayed.
    67 ==== Email Address Grantee ====
     65=== Email Address Grantee ===
    6866If 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.
    69 ==== All Users Group Grantee ====
     67=== All Users Group Grantee ===
    7068You 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.
    7169
    7270If [wiki:help/en/howto/s3#BucketAccessLogging 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`.
    7371
    74 === Versions ===
     72== Versions ==
    7573[http://aws.amazon.com/s3/faqs/#What_is_Versioning 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''.
    7674
    77 ==== Revert ====
     75=== Revert ===
    7876To revert to a previous version and make it the current, choose ''File → Revert''.
    7977
    80 ==== Multi-Factor Authentication (MFA) Delete ====
     78=== Multi-Factor Authentication (MFA) Delete ===
    8179To enable ''Multi-Factor Authentication (MFA) Delete'', you need to purchase a compatible [http://aws.amazon.com/mfa/ 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.
    8280
    83 === Signed URLs ===
    84 
     81== Public URLs ==
     82=== Signed temporary URLs ===
    8583Copy the signed URL from ''File → Info → S3''. Public access to the URL is granted for 24 hours by default.
    8684
    … …  
    9593Use ''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.
    9694
    97 === Metadata ===
     95== Metadata ==
    9896
    9997You can edit standard HTTP headers and add [wiki:help/en/howto/info#MetadataHTTPheaders custom HTTP headers] to files to store [http://docs.amazonwebservices.com/AmazonS3/latest/index.html?UsingMetadata.html metadata]. Choose ''File → Info → S3'' to edit headers.
    10098
     99Refer to the [wiki:help/en/howto/info#MetadataHTTPheaders Info panel] wiki page.
    101100
    102101=== Cache Control Setting ===
    … …  
    104103This 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.
    105104
    106 The default setting to choose from in the ''File → Info'' panel in Cyberduck is `Cache-Control: public,max-age=2052000` which translates to a cache expiration of one month (one month in seconds equals more or less `60*60*24*30`).
     105The default setting is `Cache-Control: public,max-age=2052000` when choosing to add a custom `Cache-Control` header in the [wiki:help/en/howto/info Info] panel which translates to a cache expiration of one month (one month in seconds equals more or less `60*60*24*30`).
    107106
    108107 * Use the [wiki:help/en/howto/preferences#Hiddenconfigurationoptions hidden configuration option] `s3.cache.seconds` to set a custom default value