OpenObserve announces the release of two Terraform modules that together cover both deploying OpenObserve itself and managing resources inside it. Previously, teams had to manage streams, dashboards, users, and organizations manually through the UI or API, and OpenObserve Kubernetes deployments required hand-written Helm values and infrastructure scripts. With these two Apache 2.0 licensed modules, observability infrastructure can now go through the same plan, apply, and review cycle as every other piece of your infrastructure.

The terraform-provider-openobserve, available on the Terraform Registry, lets you manage OpenObserve resources as code: streams, dashboards, users, and organizations. Define a stream with its retention policy, full-text search keys, and index fields in a .tf file, and changes follow the standard Terraform workflow with plan and apply. The terraform-kubernetes-openobserve module handles deploying OpenObserve on Kubernetes via the official Helm chart, covering both a minimal single-node SQLite setup for local development and a full production HA configuration with PostgreSQL, NATS, S3, Ingress, and per-component replica counts and resource limits. Set create_aws_infrastructure = true and the module provisions the VPC, EKS cluster, S3 bucket, and IAM roles from scratch.

The two modules are complementary: use the Kubernetes module to stand up and manage the platform, and the provider to manage what runs inside it. OpenTofu is supported alongside Terraform. Both modules are available immediately on the Terraform Registry with full documentation and examples.