About the Integration:
Cribl adds a native IBM Cloud Object Storage destination so teams can send data directly to IBM COS with an integration tailored for that platform rather than depending on generic S3 compatibility alone. The result is a cleaner path for IBM storage, archival, and cost-optimized routing workflows where reliability and straightforward configuration matter.
Benefits and Use Cases:
Support archival and lower-cost storage routing strategies for telemetry data.
Configure IBM-specific endpoint behavior instead of assuming full parity with every S3-compatible service.
Reduce integration friction for IBM Cloud storage workflows across observability and security pipelines.
How to Get Data Flowing:
Create or identify the IBM COS bucket you want to use, then generate a service ID with HMAC credentials enabled for that bucket.
Grant the service ID permission to write objects and inspect bucket metadata, and include multipart upload permissions if you expect larger file uploads.
Add a new IBM Cloud Object Storage Destination in Cribl Stream, then enter a unique Output ID, the required IBM COS endpoint, and the existing bucket name.
Store the HMAC access key and secret in Cribl secrets, attach that secret key pair to the destination, and note that IAM role-based or AssumeRole authentication is not supported for this destination.
Configure the data format, prefix or partitioning, compression, and any staging or advanced controls you need, then save and deploy the configuration. Ensure outbound HTTPS connectivity to the selected IBM COS endpoint.
Verify delivery with Run Test or Live Data, confirm objects land in the bucket, and if validation fails, review permissions, certificate trust, or the Verify if bucket exists setting.