Server access logs are written to the bucket of your choice, which can be the bucket from which the logs originate or a different bucket. If you choose a different bucket, it must have the same owner as the source bucket. Otherwise, no logs will be delivered.
The source and the target buckets must be in the same location. For more information about bucket location constraints, see How to Select a Region for Your Buckets.
When a log file is delivered to the target bucket, it is stored under a key in the following format.
In the key, YYYY, mm, DD, HH, MM and SS are the digits of the year, month, day, hour, minute, and seconds (respectively) when the log file was delivered.
A log file delivered at a specific time can contain records written at any point before that time. There is no way to know whether all log records for a certain time interval have been delivered or not.
The TargetPrefix component of the key is a string provided by the bucket owner using the logging configuration API. For more information, see Server Access Logging Configuration API.
The UniqueString component of the key carries no meaning and should be ignored by log processing software.
The system does not delete old log files. If you do not want server logs to
accumulate, you must delete them yourself. To do so, use the List operation
prefix parameter to locate old logs to delete. For more
information, see Listing Keys.