We have updated our Terms of Service, Code of Conduct, and Addendum.

Can ' t set up AWS S3 destination in Cribl using Hybrid Workers

Hassan Thiam
Hassan Thiam Posts: 15 ✭
edited December 19 in General Discussions

Hi ,

I ' m looking to add AWS S3 as a destination in Cribl while using a set of Hybrid Workers.

I have followed the below instructions but yet failing to successfully test the connection .

https://cribl.io/blog/securely-connecting-aws-s3-destination-to-cribl-cloud-and-hybrid-workers/

The logs are showing the following errors even though the AWS Roles / Permissions / Policies have been correctly applied . The resources also appear to be sufficient on the Hybrid Workers nodes .

This has worked fine with the Cribl Cloud managed workers .

Can anyone please advise ?

image.png

Tagged:

Comments

  • Jon Rust
    Jon Rust Posts: 475 mod

    It's definitely a permissions issue. The role you're using doesn't have access. You'll want to review your policy definitions again.

    Or use Cribl Lake. The easy button for using object store for logs. Free for up to 50 GB.

  • Hassan Thiam
    Hassan Thiam Posts: 15 ✭

    Good Morning ,

    The error message would suggest so indeed , I have reviewed the config which appears to be on point . Will take another look .

    I understand Cribl Lake is an option , how is the communication to Cribl Lake being secured ?

    Also would like to know if the hybrid workers can establish a private connection to their Cribl managed leader within AWS instead of having to go through the public internet ?

    Thank you

  • Jon Rust
    Jon Rust Posts: 475 mod

    The Cribl Lake storage is created inside the same AWS account as the Cribl Cloud service. Each CC account is wholly separate. All comms to the Lake are over https.

    We do not currently support private links. It's on the radar.

  • Hassan Thiam
    Hassan Thiam Posts: 15 ✭

    Thank you for your input as ever .

Categories