AWS AmazonCloudFront documentation change
Summary
Restructured steps for enabling standard logging, moved cookie logging configuration to a separate step, and added note about AWS Glue requiring lowercase distribution ID
Security assessment
The changes clarify logging setup procedures and UI navigation but do not address security vulnerabilities or add security-specific documentation. The AWS Glue note relates to syntax requirements, not security controls.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/standard-logging.md b/AmazonCloudFront/latest/DeveloperGuide/standard-logging.md index 7bc9c00e2..d39ace679 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/standard-logging.md +++ b//AmazonCloudFront/latest/DeveloperGuide/standard-logging.md @@ -91 +91 @@ To enable standard logging, you can use the CloudFront console or the CloudWatch - 1. Use the CloudFront console to create a [new distribution](./distribution-web-creating-console.html) or [update an existing one](./HowToUpdateDistribution.html#HowToUpdateDistributionProcedure). + 1. Use the CloudFront console to [update an existing distribution](./HowToUpdateDistribution.html#HowToUpdateDistributionProcedure). @@ -93 +93 @@ To enable standard logging, you can use the CloudFront console or the CloudWatch - 2. Under the **Standard logging** section, for **Log delivery** , choose **On**. + 2. Choose the **Logging** tab. @@ -95,7 +95 @@ To enable standard logging, you can use the CloudFront console or the CloudWatch - 3. (Optional) For **Cookie logging** , specify if you want to include cookies in your logs. - -###### Tip - -Cookie logging is a global setting that applies to _all_ standard logging for your distribution. You can’t override this setting for separate delivery destinations. - - 4. For the **Deliver to** section, specify the service to receive your logs: + 3. Choose **Add** , then select the service to receive your logs: @@ -109 +103 @@ Cookie logging is a global setting that applies to _all_ standard logging for yo - 5. For the **Destination** , select the resource for your service. If you haven’t already created your resource, you can choose **Create** or see the following documentation. + 4. For the **Destination** , select the resource for your service. If you haven’t already created your resource, you can choose **Create** or see the following documentation. @@ -121 +115 @@ To specify a prefix, enter the prefix after the bucket name, such as `amzn-s3-de - 6. For **Additional settings – _optional_** , you can specify the following options: + 5. For **Additional settings – _optional_** , you can specify the following options: @@ -137 +131 @@ If you choose **Parquet** , this option incurs CloudWatch charges for converting - 7. Complete the steps to update or create your distribution. + 6. Complete the steps to update or create your distribution. @@ -139 +133 @@ If you choose **Parquet** , this option incurs CloudWatch charges for converting - 8. To add another destination, choose **Add another destination** and repeat steps 4 – 7. + 7. To add another destination, repeat steps 3–6. @@ -141 +135 @@ If you choose **Parquet** , this option incurs CloudWatch charges for converting - 9. From the **Logs** page, verify that the standard logs status is **Enabled** next to the distribution. + 8. From the **Logs** page, verify that the standard logs status is **Enabled** next to the distribution. @@ -143 +137 @@ If you choose **Parquet** , this option incurs CloudWatch charges for converting -For more information about the standard logging delivery and log fields, see the [Standard logging reference](./standard-logs-reference.html). + 9. (Optional) To enable cookie logging, choose **Manage** , **Settings** and turn on **Cookie logging** , then choose **Save changes**. @@ -144,0 +139 @@ For more information about the standard logging delivery and log fields, see the +###### Tip @@ -145,0 +141 @@ For more information about the standard logging delivery and log fields, see the +Cookie logging is a global setting that applies to _all_ standard logging for your distribution. You can’t override this setting for separate delivery destinations. @@ -147,0 +144,4 @@ For more information about the standard logging delivery and log fields, see the + + +For more information about the standard logging delivery and log fields, see the [Standard logging reference](./standard-logs-reference.html). + @@ -648 +648 @@ You can use the following variables to create a folder path. - * `{DistributionId}` + * `{DistributionId}` or `{distributionid}` @@ -673,0 +674,4 @@ You can use any number of variables and specify folder names in your path. Cloud +###### Note + +You can use either variable for distribution ID in the suffix path. However, if you're sending access logs to AWS Glue, you must use the `{distributionid}` variable because AWS Glue expects partition names to be in lowercase. Update your existing log configuration in CloudFront to replace `{DistributionId}` with `{distributionid}`. +