Executive Summary

This document provides an overview of how Disaster Recovery (DR) is structured, and what the primary and standby roles do.

Two clusters are managed via Terraform workspaces:

  • Primary (us-chicago-1): production, dr="active".

  • Secondary (us-chicago-1): standby, dr="standby", minimal capacity, reads the primary's Object Storage bucket using the exact same encryption key pulled via remote state, and keeps all LogScale pods scaled to zero until a failover/promotion is initiated.

Region flexibility

The regions shown are examples only. You can deploy in any OCI regions supported by your organization.

Update region in your tfvars, the remote state configuration, and any region-specific references to match your chosen regions.

Key Features

  • Automated encryption key synchronization (no hardcoding). Standby apply requires the primary key (remote state or explicit value).

  • Cross-region Object Storage access via IAM policies.

  • Alerts toggle automatically via ENABLE_ALERTS based on dr.

  • Standby keeps Humio Operator scaled to 0; OCI Function (or manual) scales the operator to 1 on failover.

  • Manual, controlled promotion by changing dr and applying Terraform.

Key Capabilities
FeaturePrimary (Active)Secondary (Standby)
Regionus-chicago-1us-chicago-1
Cluster TypeAdvanced (full production)Standby (Humio Operator off)
Humio nodeCountcluster_size digest countnodeCount=1 declared, but no pods run until operator is scaled up
Humio operator1 replica0 replicas until failover
Replication FactorProduction value1 (overridden)
Auto RebalanceEnabledDisabled
Object Storage Bucketdr-primary-logscale-datadr-secondary-logscale-data
Encryption KeyGenerated on first deployPulled from primary state (required for standby apply)
Terraform Workspaceprimarysecondary
DR Modedr = "active"dr = "standby"

Note

The dr variable accepts three values:

  • "active" - Primary cluster in a DR pair

  • "standby" - Secondary cluster in a DR pair (minimal capacity, operator scaled to 0)

  • "" (empty string) - Non-DR single cluster deployment (no DR infrastructure provisioned)