AWS::CloudFront::Distribution Logging
A complex type that specifies whether access logs are written for the distribution.
Note
If you already enabled standard logging (legacy) and you want to enable standard logging (v2) to send your access logs to Amazon S3, we recommend that you specify a different Amazon S3 bucket or use a separate path in the same bucket (for example, use a log prefix or partitioning). This helps you keep track of which log files are associated with which logging subscription and prevents log files from overwriting each other. For more information, see Standard logging (access logs) in the Amazon CloudFront Developer Guide.
Syntax
To declare this entity in your Amazon CloudFormation template, use the following syntax:
JSON
{ "Bucket" :
String
, "IncludeCookies" :Boolean
, "Prefix" :String
}
YAML
Bucket:
String
IncludeCookies:Boolean
Prefix:String
Properties
Bucket
-
The Amazon S3 bucket to store the access logs in, for example,
amzn-s3-demo-bucket.s3.amazonaws.com
.Required: No
Type: String
Update requires: No interruption
-
Specifies whether you want CloudFront to include cookies in access logs, specify
true
forIncludeCookies
. If you choose to include cookies in logs, CloudFront logs all cookies regardless of how you configure the cache behaviors for this distribution. If you don't want to include cookies when you create a distribution or if you want to disable include cookies for an existing distribution, specifyfalse
forIncludeCookies
.Required: No
Type: Boolean
Update requires: No interruption
Prefix
-
An optional string that you want CloudFront to prefix to the access log
filenames
for this distribution, for example,myprefix/
. If you want to enable logging, but you don't want to specify a prefix, you still must include an emptyPrefix
element in theLogging
element.Required: No
Type: String
Update requires: No interruption
See also
-
LoggingConfig in the Amazon CloudFront API Reference