Requirements
See also the Operations Guide.
Software Requirements
| Component | Minimum Version | Purpose |
|---|---|---|
| Terraform | >= 1.5 | Infrastructure provisioning |
| kubectl | >= 1.25 | Kubernetes cluster management |
| AWS CLI | >= 2.0 | AWS resource access and authentication |
| Helm | >= 3.10 | Kubernetes package management |
| jq | >= 1.6 | JSON processing for verification scripts |
AWS Account Requirements
| Requirement | Description |
|---|---|
| AWS Account | Single AWS account with access to both primary and secondary regions |
| Regions | Two AWS regions (e.g., us-west-2 and us-east-2) with EKS availability |
| Service Quotas | Sufficient EC2, EBS, and EKS quotas in both regions |
| Route53 Hosted Zone | Public hosted zone for global DNS failover records |
Infrastructure Requirements
| Component | Requirement | Notes |
|---|---|---|
| Terraform Backend | S3 bucket + DynamoDB lock table | Must be accessible from both regions |
| VPC/Networking | VPC with public/private subnets in each region | EKS requires specific subnet configurations |
| EKS Clusters | Base EKS clusters provisioned | DR module layers on top of existing clusters |
| ACM Certificates | Valid certificates for LogScale endpoints | Can use Let's Encrypt via cert-manager |
Encryption Key Requirements
The secondary cluster requires access to the primary's S3 encryption key for DR recovery. Three methods are supported: remote state (recommended), TFE outputs, or an explicit key variable.
For the full encryption key configuration table, key lifecycle details, and the pre-install validation that enforces key availability, see Encryption Key Requirements.