Logging actions with a bucket
In ColdStack, there is an option to log all actions with a bucket. You can record logs, for example, to run an internal security audit or get more granular information about bucket operations.
Logging is disabled by default. After you enable this option, ColdStack will write actions with the bucket to an object once an hour.
To save logs, do the following:
The source and target buckets must be in the same region.
ColdStack uses the following format of the key for the log object:
prefix: The prefix of the key for the log object. You can specify your own prefix when enabling logging.
YYYY-MM-DD-HH-MM-SS: Date and time of saving the log object in the target bucket (UTC format).
ID: A unique record ID that prevents the object from being overwritten.
The key prefix lets you distinguish:
- Data belonging to different buckets, if the logs for multiple source buckets are saved to the same target bucket.
- Logging actions from other actions with the bucket, if the logs are saved to the source bucket. That's because the logging operation is also considered an action with the bucket in this case.
Logs are saved to a text file. For every action with the bucket, a record is written to the file in the following format:
There are several points to note about how actions with a bucket are logged in ColdStack.
Most requests to a bucket are written to the log file (if the bucket was set up correctly to support logging). Most records are written within a few hours after the request is actually processed.
However, ColdStack doesn't guarantee that the logs are saved in a complete and timely manner. It may take several hours to record an action with the bucket in a log file. In some cases, a record might fail to appear in the file.
The log file provides an overview of the nature of traffic in the bucket, but is not intended for logging every request. In the payment documents, you can find several requests that are not saved in the log file.
The standard ColdStack pricing rules apply to logging.