Amazon CloudWatch Logs now supports Network Load Balancer (NLB) access logs as vended logs, improving observability and simplifying debugging for network traffic patterns. You can now analyze NLB access logs directly in CloudWatch to gain insights into client connections, traffic distribution, and connection status, helping you identify and troubleshoot network issues faster.
With this CloudWatch Logs integration, you can track detailed access patterns using CloudWatch Logs Insights queries, create metric filters for monitoring, and review traffic patterns in real time using Live Tail. NLB access logs can be configured through the integrations tab of your network load balancer in AWS Management Console, AWS CLI, or SDKs. You can also configure delivery of NLB access logs to Amazon Data Firehose or Amazon S3 with support for Apache Parquet format.
NLB access logs delivery to CloudWatch is available in all AWS Commercial and GovCloud regions where Network Load Balancer and CloudWatch are available. NLB access logs are charged as vended logs when delivered to CloudWatch Logs and Data Firehose, while delivery to Amazon S3 is free (Parquet conversion is charged at $0.035/GB – N. Virginia).
To learn more about configuring NLB access logs in CloudWatch Logs, please visit our documentation. For pricing information, see CloudWatch pricing page.
Categories: general:products/amazon-cloudwatch,marketing:marchitecture/management-and-governance
Source: Amazon Web Services
Latest Posts
- (Updated) Microsoft Edge: Microsoft 365 Copilot will support summarization and contextual grounding [MC1187682]
- (Updated) Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces [MC929022]
- (Updated) Rewrite with Microsoft 365 Copilot Chat coming soon to Edge for Business users [MC1146821]
- Interpreter agent in Teams calls [MC1191612]
