Cyberduck Mountain Duck CLI

Changes between Version 24 and Version 25 of help/en/howto/s3


Ignore:
Timestamp:
Jul 10, 2009 1:16:39 PM (12 years ago)
Author:
dkocher
Comment:

--

Legend:

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

    v24 v25  
    4747This 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.
    4848
    49 The default setting to choose from in the ''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`).
     49The 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`).
    5050
    5151 * Read more about [http://docs.amazonwebservices.com/AmazonCloudFront/latest/DeveloperGuide/index.html?Expiration.html Amazon CloudFront Object Expiration].
     
    5353=== Bucket Access Logging (New in ''3.2.1'') ===
    5454
    55 When this option is enabled in the ''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`.
     55When 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`.
    5656
    5757Citing the Amazon S3 [http://docs.amazonwebservices.com/AmazonS3/2006-03-01/index.html?LoggingHowTo.html documentation]:
     
    6060=== CloudFront Access Logging (New in ''3.2.1'') ===
    6161
    62 When this option is enabled in the ''Info'' panel of a bucket or any file within, the access logs of the enabled distribution are written to `<bucketname>/logs`. The changes to your distribution's logging configuration take effect within 12 hours.
     62When this option is enabled in the ''File →  Info'' panel of a bucket or any file within, the access logs of the enabled distribution are written to `<bucketname>/logs`. The changes to your distribution's logging configuration take effect within 12 hours.
    6363
    6464Citing the Amazon CloudFront [http://docs.amazonwebservices.com/AmazonCloudFront/2009-04-02/DeveloperGuide/index.html?AccessLogs.html documentation]: ''Access logs are activity records that show you details about every request delivered through Amazon CloudFront. They contain a comprehensive set of information about requests for your content, including the object requested, the date and time of the request, the edge location serving the request, the client IP address, the referrer and the user agent. Access logging is an optional feature of CloudFront. There is no extra charge for enabling access logging. However, you accrue the usual Amazon S3 charges for storing and accessing the files (you can delete them at any time). With CloudFront logging (unlike with Amazon S3 server access logging), you also accrue Amazon S3 data transfer charges for each log file that CloudFront writes to your bucket.