OpenObserve announces Bring Your Own Bucket (BYOB), a new capability that lets commercial Cloud customers connect their own object storage directly to OpenObserve. Previously, all telemetry data ingested through OpenObserve Cloud was stored in OpenObserve-managed storage, which meant customers had limited control over data locality, security policies, and existing cloud storage commitments. With BYOB, you can now attach your own S3 bucket or Azure Blob container, and OpenObserve handles ingestion, compaction, and queries against it — while your data remains in your account, in your region, under your own access controls.

This capability unlocks several critical use cases. For data residency and compliance, teams can keep telemetry in a specific region or jurisdiction without workarounds. For cost control, organizations can leverage reserved capacity, existing storage commitments, or negotiated cloud rates they already have. For data ownership, raw telemetry data remains yours, independent of the observability platform. And for portability, there is no vendor lock-in on storage — migrate or switch without a data migration project.

The customer’s storage bucket must reside in the same region and use the same cloud provider as the OpenObserve Cloud deployment it connects to. For example, an OpenObserve Cloud running on AWS us-west-1 can only use an AWS S3 bucket in us-west-1, and an Azure East US 2 deployment can only use an Azure Blob Storage container in East US 2. Cross-region and cross-provider configurations are not supported. Setup is available from the OpenObserve Cloud settings by providing your bucket details and access credentials. BYOB is available for commercial OpenObserve Cloud customers. To enable this capability for your organization, contact us.