You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/radosgw/bucket_logging.rst
+46Lines changed: 46 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,12 @@ in different objects in the log bucket.
20
20
- The log bucket must be created before enabling logging on a bucket
21
21
- The log bucket cannot be the same as the bucket being logged
22
22
- The log bucket cannot have logging enabled on it
23
+
- The log bucket cannot have any encryption set on in (including SSE-S3 with AES-256)
24
+
- The log bucket cannot have any compression set on it
25
+
- The log bucket must not have RequestPayer enabled
26
+
- Source and log bucket must be in the same zonegroup
27
+
- Source and log buckets may belong to different accounts (with proper bucket policy set)
28
+
- The log bucket may have object lock enabled with default retention period
23
29
24
30
25
31
.. toctree::
@@ -51,6 +57,46 @@ Journal mode supports filtering out records based on matches of the prefixes and
51
57
Note that it may happen that the log records were successfully written, but the bucket operation failed, since the logs are written.
52
58
53
59
60
+
Bucket Logging Policy
61
+
---------------------
62
+
On the source bucket, only its owner is allowed to enable or disable bucket logging.
63
+
For a bucket to be used as a log bucket, it must have bucket policy that allows that (even if the source bucket and the log bucket are owned by the same user or account).
64
+
The bucket policy must allow the `s3:PutObject` action for the log bucket, to be perfomed by the `logging.s3.amazonaws.com` service principal.
65
+
It should also specify the source bucket and account that are expected to write logs to it. For example:
Bucket and user quota are applied on the log bucket. Quota is checked every time a log record is written,
96
+
and updated when the log object is added to the log bucket. In "Journal" mode, if the quota is exceeded, the logging operation will fail
97
+
and as a result the bucket operation will also fail. In "Standard" mode, the logging operation will be skipped, but the bucket operation will continue.
0 commit comments