class Aws::S3::Types::LoggingEnabled
Describes where logs are stored and the prefix that Amazon S3
assigns to all log object keys for a bucket. For more information, see [PUT Bucket
logging] in the *Amazon S3
API Reference*.
[1]: docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTlogging.html
@note When making an API call, you may pass LoggingEnabled
data as a hash: { target_bucket: "TargetBucket", # required target_grants: [ { grantee: { display_name: "DisplayName", email_address: "EmailAddress", id: "ID", type: "CanonicalUser", # required, accepts CanonicalUser, AmazonCustomerByEmail, Group uri: "URI", }, permission: "FULL_CONTROL", # accepts FULL_CONTROL, READ, WRITE }, ], target_prefix: "TargetPrefix", # required }
@!attribute [rw] target_bucket
Specifies the bucket where you want Amazon S3 to store server access logs. You can have your logs delivered to any bucket that you own, including the same bucket that is being logged. You can also configure multiple buckets to deliver their logs to the same target bucket. In this case, you should choose a different `TargetPrefix` for each source bucket so that the delivered log files can be distinguished by key. @return [String]
@!attribute [rw] target_grants
Container for granting information. @return [Array<Types::TargetGrant>]
@!attribute [rw] target_prefix
A prefix for all log object keys. If you store log files from multiple Amazon S3 buckets in a single bucket, you can use a prefix to distinguish which log files came from which bucket. @return [String]
@see docs.aws.amazon.com/goto/WebAPI/s3-2006-03-01/LoggingEnabled AWS API Documentation
Constants
- SENSITIVE