AWS elasticloadbalancing documentation change
Summary
Added CloudWatch Logs integration and updated field names in access log documentation
Security assessment
Enhanced logging capabilities improve security monitoring but there's no evidence of addressing a specific vulnerability. Field name changes are documentation improvements without security implications.
Diff
diff --git a/elasticloadbalancing/latest/network/load-balancer-access-logs.md b/elasticloadbalancing/latest/network/load-balancer-access-logs.md index 3147c3273..2132de3e1 100644 --- a//elasticloadbalancing/latest/network/load-balancer-access-logs.md +++ b//elasticloadbalancing/latest/network/load-balancer-access-logs.md @@ -12,0 +13,4 @@ Elastic Load Balancing provides access logs that capture detailed information ab +While traditional "legacy" access logs (described in this section) remain available, Network Load Balancer now offers enhanced logging options through CloudWatch Logs. CloudWatch Logs provide more flexible delivery options, including to Amazon CloudWatch Logs, Amazon Data Firehose, and Amazon Simple Storage Service. To configure these improved logging options, visit your load balancer's _**Integrations**_ tab. For more information on CloudWatch Logs, see [CloudWatch logs for your Network Load Balancer](./load-balancer-cloudwatch-logs.html). + +###### Important + @@ -103,2 +107,2 @@ listener | The resource ID of the TLS listener for the connection. -client:port | The IP address and port of the client. -destination:port | The IP address and port of the destination. If the client connects directly to the load balancer, the destination is the listener. If the client connects using a VPC endpoint service, the destination is the VPC endpoint. +client_port | The IP address and port of the client. +destination_port | The IP address and port of the destination. If the client connects directly to the load balancer, the destination is the listener. If the client connects using a VPC endpoint service, the destination is the VPC endpoint.