A web app uses an ALB across multiple AZs with Lambda targets and CloudWatch metrics. Some users report parts of the app aren't loading. The engineer has enabled ALB access logging. What should the engineer do next to identify which errors the ALB is logging?

The correct approach is to configure an S3 bucket for ALB access logs and then use Amazon Athena to query them. ALB access logs provide detailed information, including HTTP status codes and error messages, which are crucial for troubleshooting. Athena is a serverless query service that allows you to analyze data directly in S3 using standard SQL, making it efficient for large log files. Sending logs directly to CloudWatch Logs for ALB access logs is not a native or recommended configuration; ALB access logs are typically delivered to S3. While CloudWatch Logs Insights can analyze logs within CloudWatch Logs, it's not the primary mechanism for ALB access logs. CloudWatch Logs does not automatically pull ALB logs from S3; a separate integration or service would be needed, which adds unnecessary complexity. The Amazon Athena CloudWatch Connector is for querying CloudWatch Logs data with Athena, not for querying ALB access logs stored in S3.