AWS elasticloadbalancing documentation change
Summary
Updated log file name examples (replaced '.' with '_' in filenames) and added field position numbers in connection log entry documentation table
Security assessment
Changes are documentation formatting improvements (filename examples and table field numbering). No evidence of addressing vulnerabilities or security incidents. TLS-related field descriptions remain unchanged except for positional numbering.
Diff
diff --git a/elasticloadbalancing/latest/application/load-balancer-connection-logs.md b/elasticloadbalancing/latest/application/load-balancer-connection-logs.md index d7458e14b..79bebae8b 100644 --- a//elasticloadbalancing/latest/application/load-balancer-connection-logs.md +++ b//elasticloadbalancing/latest/application/load-balancer-connection-logs.md @@ -94 +94 @@ The following is an example log file name with a prefix: - s3://amzn-s3-demo-logging-bucket/logging-prefix/AWSLogs/123456789012/elasticloadbalancing/us-east-2/2022/05/01/conn_log.123456789012_elasticloadbalancing_us-east-2_app.my-loadbalancer.1234567890abcdef_20220215T2340Z_172.160.001.192_20sg8hgm.log.gz + s3://amzn-s3-demo-logging-bucket/logging-prefix/AWSLogs/123456789012/elasticloadbalancing/us-east-2/2022/05/01/conn_log_123456789012_elasticloadbalancing_us-east-2_app.my-loadbalancer.1234567890abcdef_20220215T2340Z_172.160.001.192_20sg8hgm.log.gz @@ -99 +99 @@ The following is an example log file name without a prefix: - s3://amzn-s3-demo-logging-bucket/AWSLogs/123456789012/elasticloadbalancing/us-east-2/2022/05/01/conn_log.123456789012_elasticloadbalancing_us-east-2_app.my-loadbalancer.1234567890abcdef_20220215T2340Z_172.160.001.192_20sg8hgm.log.gz + s3://amzn-s3-demo-logging-bucket/AWSLogs/123456789012/elasticloadbalancing/us-east-2/2022/05/01/conn_log_123456789012_elasticloadbalancing_us-east-2_app.my-loadbalancer.1234567890abcdef_20220215T2340Z_172.160.001.192_20sg8hgm.log.gz @@ -120 +120 @@ The following table describes the fields of a connection log entry, in order. Al -Field | Description +Field (position) | Description @@ -122,7 +122,7 @@ Field | Description -timestamp | The time, in ISO 8601 format, when the load balancer successfully established or failed to establish a connection. -client_ip | The IP address of the requesting client. -client_port | The port of the requesting client. -listener_port | The port of the load balancer listener receiving the client request. -tls_protocol | [HTTPS listener] The SSL/TLS protocol used during handshakes. This field is set to `-` for non SSL/TLS requests. -tls_cipher | [HTTPS listener] The SSL/TLS protocol used during handshakes. This field is set to `-` for non SSL/TLS requests. -tls_handshake_latency | [HTTPS listener] The total time in seconds, with a millisecond precision, elapsed while establishing a successful handshake. This field is set to `-` when: +timestamp (1) | The time, in ISO 8601 format, when the load balancer successfully established or failed to establish a connection. +client_ip (2) | The IP address of the requesting client. +client_port (3) | The port of the requesting client. +listener_port (4) | The port of the load balancer listener receiving the client request. +tls_protocol (5) | [HTTPS listener] The SSL/TLS protocol used during handshakes. This field is set to `-` for non SSL/TLS requests. +tls_cipher (6) | [HTTPS listener] The SSL/TLS protocol used during handshakes. This field is set to `-` for non SSL/TLS requests. +tls_handshake_latency (7) | [HTTPS listener] The total time in seconds, with a millisecond precision, elapsed while establishing a successful handshake. This field is set to `-` when: @@ -134 +134 @@ tls_handshake_latency | [HTTPS listener] The total time in seconds, with a mill -leaf_client_cert_subject | [HTTPS listener] The subject name of the leaf client certificate. This field is set to `-` when: +leaf_client_cert_subject (8) | [HTTPS listener] The subject name of the leaf client certificate. This field is set to `-` when: @@ -141 +141 @@ leaf_client_cert_subject | [HTTPS listener] The subject name of the leaf client -leaf_client_cert_validity | [HTTPS listener] The validity, with `not-before` and `not-after` in ISO 8601 format, of the leaf client certificate. This field is set to `-` when: +leaf_client_cert_validity (9) | [HTTPS listener] The validity, with `not-before` and `not-after` in ISO 8601 format, of the leaf client certificate. This field is set to `-` when: @@ -148 +148 @@ leaf_client_cert_validity | [HTTPS listener] The validity, with `not-before` an -leaf_client_cert_serial_number | [HTTPS listener] The serial number of the leaf client certificate. This field is set to `-` when: +leaf_client_cert_serial_number (10) | [HTTPS listener] The serial number of the leaf client certificate. This field is set to `-` when: @@ -155,2 +155,2 @@ leaf_client_cert_serial_number | [HTTPS listener] The serial number of the leaf -tls_verify_status | [HTTPS listener] The status of the connection request. This value is `Success` if the connection is established successfully. On an unsuccessful connection the value is `Failed:$error_code`. -conn_trace_id | The connection traceability ID is a **unique opaque ID** used to identify each connection. After a connection is established with a client, subsequent requests from this client contain this ID in their respective access log entries. This ID acts as a foreign key to create a link between the connection and access logs. +tls_verify_status (11) | [HTTPS listener] The status of the connection request. This value is `Success` if the connection is established successfully. On an unsuccessful connection the value is `Failed:$error_code`. +conn_trace_id (12) | The connection traceability ID is a **unique opaque ID** used to identify each connection. After a connection is established with a client, subsequent requests from this client contain this ID in their respective access log entries. This ID acts as a foreign key to create a link between the connection and access logs.