AWS S3 Collector versus S3 Input SQS - Which to Pick?
You’ve got logs landing in S3 — maybe CloudTrail, maybe Snowflake, maybe Crowdstrike FDR as examples. The question that inevitably comes up is: “Should we use an S3 Collector or an Amazon S3 Source (via SQS) to get them into Cribl Stream?” It’s a great question, and like many things in the security and observability space, the answer depends on how you want to work with your data. Let’s break it down. What’s an S3 Collector Source? Think of the S3 Collector Source as a batch retrieval engine. It’s perfect when you need to reach back in time and grab a chunk of data from S3 — say, “get me three hours of logs from noon yesterday for host==abcd.” It doesn’t care about real-time ingestion or message queues. You tell it what timeframe and what filters you want, and it goes and gets them, either on demand or on a schedule. Ideal when you:Need to rehydrate historical logs (for example, for a retroactive investigation)	Want to replay old data for validation, benchmarking, or pipeline testing	W