AWS Security ChangesHomeSearch

AWS elasticloadbalancing documentation change

Service: elasticloadbalancing · 2025-07-04 · Documentation low

File: elasticloadbalancing/latest/application/load-balancer-access-logs.md

Summary

Added Trace ID (TID) field to all access log examples and clarified example formatting

Security assessment

The addition of TID fields enhances traceability between connection and access logs, aiding security investigations. While this improves audit capabilities, it does not address a specific security vulnerability.

Diff

diff --git a/elasticloadbalancing/latest/application/load-balancer-access-logs.md b/elasticloadbalancing/latest/application/load-balancer-access-logs.md
index ffb853e29..9af51d052 100644
--- a//elasticloadbalancing/latest/application/load-balancer-access-logs.md
+++ b//elasticloadbalancing/latest/application/load-balancer-access-logs.md
@@ -290 +290 @@ Code | Description
-The following are example log entries. Note that the text appears on multiple lines only to make them easier to read.
+The following are example log entries. Note that the example text appears on multiple lines only to make them easier to read.
@@ -302 +302 @@ The following is an example log entry for an HTTP listener (port 80 to port 80):
-    0 2018-07-02T22:22:48.364000Z "forward" "-" "-" "10.0.0.1:80" "200" "-" "-"
+    0 2018-07-02T22:22:48.364000Z "forward" "-" "-" "10.0.0.1:80" "200" "-" "-" TID_1234abcd5678ef90
@@ -314 +314 @@ The following is an example log entry for an HTTPS listener (port 443 to port 80
-    1 2018-07-02T22:22:48.364000Z "authenticate,forward" "-" "-" "10.0.0.1:80" "200" "-" "-" TID_123456
+    1 2018-07-02T22:22:48.364000Z "authenticate,forward" "-" "-" "10.0.0.1:80" "200" "-" "-" TID_1234abcd5678ef90
@@ -326 +326 @@ The following is an example log entry for an HTTP/2 stream.
-    1 2018-07-02T22:22:48.364000Z "redirect" "https://example.com:80/" "-" "10.0.0.66:9000" "200" "-" "-"
+    1 2018-07-02T22:22:48.364000Z "redirect" "https://example.com:80/" "-" "10.0.0.66:9000" "200" "-" "-" TID_1234abcd5678ef90
@@ -338 +338 @@ The following is an example log entry for a WebSockets connection.
-    1 2018-07-02T22:22:48.364000Z "forward" "-" "-" "10.0.1.192:8010" "101" "-" "-"
+    1 2018-07-02T22:22:48.364000Z "forward" "-" "-" "10.0.1.192:8010" "101" "-" "-" TID_1234abcd5678ef90
@@ -350 +350 @@ The following is an example log entry for a secured WebSockets connection.
-    1 2018-07-02T22:22:48.364000Z "forward" "-" "-" "10.0.0.171:8010" "101" "-" "-"
+    1 2018-07-02T22:22:48.364000Z "forward" "-" "-" "10.0.0.171:8010" "101" "-" "-" TID_1234abcd5678ef90
@@ -362 +362 @@ The following is an example log entry for a request to a Lambda function that su
-    0 2018-11-30T22:22:48.364000Z "forward" "-" "-" "-" "-" "-" "-"
+    0 2018-11-30T22:22:48.364000Z "forward" "-" "-" "-" "-" "-" "-" TID_1234abcd5678ef90
@@ -372 +372 @@ The following is an example log entry for a request to a Lambda function that fa
-    0 2018-11-30T22:22:48.364000Z "forward" "-" "LambdaInvalidResponse" "-" "-" "-" "-"
+    0 2018-11-30T22:22:48.364000Z "forward" "-" "LambdaInvalidResponse" "-" "-" "-" "-" TID_1234abcd5678ef90