This message originated from Cribl Community Slack.
Click here to view the original link.
Hi everyone, is there anything that could trip us up if we wanted to run a collect job for data stored in Amazon Security Lake S3?
Solved
Amazon Security Lake S3 Collect Job Potential Issues During Execution
Best answer by Kam Amir
We had a customer, Siemens that did the same thing. They built a cribl pack too that will help with the collection and sending of data into Splunk.
Where are you going to send it?
It's a standard sqs based s3 pull. Just make sure you use the sqs tied to the partition you want to pull from. There are technically two sqs queues and there are permissions for each one. First make sure your IAM role has access to the s3 bucket and sqs.
We've got a pull going with sqs, this is to retrieve data as a one-off using the S3 collector instead. It ends up in Splunk
We had a customer, Siemens that did the same thing. They built a cribl pack too that will help with the collection and sending of data into Splunk.
Sign up
Already have an account? Login
Login to the community
No account yet? Create an account
Using your Cribl Curious or University Account
User Login Employee loginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.