What's New in OpenObserve: Terraform Support, Kubernetes and AWS Automation, Bring Your Own Bucket, and UX Improvements
OpenObserve has shipped three major updates that help engineering teams automate observability, keep full control over telemetry data, and troubleshoot incidents faster.
In this release:
- Terraform support for managing OpenObserve deployments and resources as code
- Bring Your Own Bucket (BYOB) for Amazon S3 and Azure Blob Storage
- UX and UI improvements for logs, distributed tracing, and root cause analysis
If you run observability on Kubernetes, AWS, Azure, or other cloud environments, these updates simplify deployment, improve governance, and streamline day-to-day troubleshooting.
Terraform Support for Observability as Code
OpenObserve now includes a Terraform provider that lets you manage observability resources using infrastructure as code.
Supported resources include:
- Streams
- Dashboards
- Users and organizations
- Retention policies
- Indexed fields
- Full-text search settings
OpenObserve also provides a Kubernetes Terraform module that deploys the platform using the official Helm chart. The module supports both single-node environments and production high-availability deployments with PostgreSQL, NATS, S3, and Ingress.
For AWS users, the module can optionally provision:
- Amazon VPC
- Amazon EKS
- Amazon S3
- IAM roles
This makes it possible to manage both the observability platform and its configuration through Terraform or OpenTofu.
Bring Your Own Bucket (BYOB) for Amazon S3 and Azure Blob Storage
Commercial OpenObserve Cloud customers can now connect their own Amazon S3 bucket or Azure Blob Storage container.
Telemetry data remains in your cloud account, region, and security boundary, while OpenObserve continues to handle ingestion, compaction, and querying.
Key benefits include:
- Full ownership of logs, metrics, and traces
- Data residency and compliance control
- Better use of existing cloud storage commitments
- No storage lock-in
UX and UI Improvements for Logs and Distributed Tracing
This release also includes several improvements to help engineers move from alert to root cause more quickly.
Highlights include:
- Service Catalog
- Span details directly in the flame graph
- Better default log columns
- Multi-stream log correlation
- Smarter View Logs filters
These changes reduce the number of clicks required to investigate incidents and correlate logs and traces. Try it!
Get all the details, features, and how-tos:
This article is a summary of the latest OpenObserve release.
For screenshots, implementation details, and links to the Terraform provider and Kubernetes module, read the full announcement.