This behavior is related to how Wazuh AWS S3 integrations work by default:
VPC Flow logs: Wazuh expects a supported/standard VPC Flow log structure. If the file includes a header or a non-standard/custom field layout, parsing can fail (as seen in your invalid literal for int() with base 10: 'type' message).
NLB logs: Collection may still be working even if you do not see events in the UI. By default, visibility depends on active rules that generate alert levels shown in Security Events.
What is possible with the tool out of the box:
Ingest AWS logs from S3 (for supported log types/formats).
Decode and normalize events.
Show events in UI when matching rules produce visible alerts.
What is not automatic by default:
Handling every custom VPC Flow log format variation.
Showing all ingested NLB records in UI without matching visible rules/conditions.
Recommended operational checks:
Confirm bucket type/configuration and AWSLogs prefix/region/account path.
Verify IAM permissions for S3 read/list.
Validate the exported VPC Flow format is standard/supported.
Confirm time range, index pattern, and severity filters in the UI.
Check manager logs to confirm ingestion vs. correlation/visibility.
--
You received this message because you are subscribed to the Google Groups "Wazuh | Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wazuh/89b8bcac-f402-4e80-80c0-efc7efda43c9n%40googlegroups.com.