|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
This section describes Beta functionality that is subject to change in future releases. Please provide feedback on this functionality in the Amazon S3 Developer Forum.
An Amazon S3 bucket can be configured to create access log records for the requests made against it. An access log record contains details about the request such as the request type, the resource with which the request worked, and the time and date that the request was processed. Server access logs are useful for many applications, because they give bucket owners insight into the nature of requests made by clients not under their control.
By default, server access logs are not collected for a bucket. To learn how to enable server access logging, see Server Access Logging Configuration API.
Once logging is enabled for a bucket, available log records are aggregated into log files and delivered to you via an Amazon S3 bucket of your choosing on an hourly basis. For a detailed description of this process, see Delivery of Server Access Logs.
For information on how to interpret the contents of log files, see Server Access Log Format.
To walk through the process of enabling logging for your bucket, see Setting Up Server Access Logging.
There is no extra charge for enabling the server access logging feature on an Amazon S3 bucket, however any log files the system delivers to you will accrue the usual charges for storage (you can delete the log files at any time). No data transfer charges will be assessed for log file delivery, but access to the delivered log files is charged for data transfer in the usual way.