class Aws::S3::Types::LoggingEnabled

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