AWS AmazonCloudFront documentation change
Summary
Updated log group naming conventions to differentiate between cache behavior-level functions and distribution-level Connection Functions. Added Connection Functions log examples and corrected references from 'real-time logs' to 'real-time access logs'.
Security assessment
Changes involve log formatting and naming conventions without addressing vulnerabilities or security features. No evidence of security fixes or weaknesses being patched.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/edge-functions-logs.md b/AmazonCloudFront/latest/DeveloperGuide/edge-functions-logs.md index 10d302b87..218f7c600 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/edge-functions-logs.md +++ b//AmazonCloudFront/latest/DeveloperGuide/edge-functions-logs.md @@ -64 +64,14 @@ If a CloudFront function's code contains `console.log()` statements, CloudFront -CloudFront Functions always creates log streams in the US East (N. Virginia) Region (`us-east-1`), no matter which edge location ran the function. The log group name is in the format `/aws/cloudfront/function/`<FunctionName>``, where ``<FunctionName>`` is the name that you gave to the function when you created it. The log stream name is in the format `YYYY/M/D/`UUID``. +CloudFront Functions always creates log streams in the US East (N. Virginia) Region (`us-east-1`), no matter which edge location ran the function. The log stream name is in the format `YYYY/M/D/`UUID``. + +The log group name uses the following format: + + * For CloudFront Functions at the cache behavior level, the format is `/aws/cloudfront/function/`<FunctionName>`` + + * For CloudFront Functions at the distribution level (Connection Functions), the format is `/aws/cloudfront/connection-function/`<FunctionName>`` + + + + +The ``<FunctionName>`` is the name that you gave to the function when you created it. . + +###### Example Viewer requests @@ -72,0 +86,9 @@ The following shows an example log message sent to CloudWatch Logs. Each line be +###### Example Connection requests + +The following shows an example log message sent to CloudWatch Logs. Each line begins with an ID that uniquely identifies a CloudFront request. The message begins with a `START` line that includes the CloudFront distribution ID, and ends with an `END` line. Between the `START` and `END` lines are the log lines generated by `console.log()` statements in the function. + + + U7b4hR_RaxMADupvKAvr8_m9gsGXvioUggLV5Oyq-vmAtH8HADpjhw== START DistributionID: E3E5D42GADA123 + U7b4hR_RaxMADupvKAvr8_m9gsGXvioUggLV5Oyq-vmAtH8HADpjhw== 1.2.3.4 + U7b4hR_RaxMADupvKAvr8_m9gsGXvioUggLV5Oyq-vmAtH8HADpjhw== END + @@ -79 +101 @@ CloudFront Functions uses an AWS Identity and Access Management (IAM) [service-l -When a function fails with a validation error or an execution error, the information is logged in [standard logs](./AccessLogs.html) and [real-time logs](./real-time-logs.html). For specific information about the error, see the `x-edge-result-type`, `x-edge-response-result-type`, and `x-edge-detailed-result-type` fields. +When a function fails with a validation error or an execution error, the information is logged in [standard logs](./AccessLogs.html) and [real-time access logs](./real-time-logs.html). For specific information about the error, see the `x-edge-result-type`, `x-edge-response-result-type`, and `x-edge-detailed-result-type` fields. @@ -87 +109 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Use real-time logs +Use real-time access logs