Minimal Terraform Backend Plan (S3 + DynamoDB)
Why
- S3 stores shared Terraform state.
Loading module
Resolving locale, route permissions, and workspace projection.
Resolving locale, route permissions, and workspace projection.
Current scope: Guest
Category: 80_chain | Version: v1.0.0
Owner: DOCUMENT_CUSTODIAN | Review cycle: 60 days
Approval authority: GOVERNANCE_ADMIN, CHAIN_OFFICER
Documentation portal is read-only. Editing and mutation endpoints are disabled.
Kvary platform is originally created in Georgian. Where a Georgian version exists, Georgian is authoritative for platform UI, documentation, and legal interpretation.
Translations into other languages are provided for convenience. Some records may originate in other languages and carry their own source or legal locale for a specific flow, but where a Georgian version is available, the Georgian version prevails for platform-level wording and interpretation.
Metadata incomplete: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log
apply corruption.This does not change runtime architecture (EC2/ECS stays the same).
Create S3 bucket and DynamoDB lock table per env (dev, stage, prod):
kvary-terraform-state-<env>kvary-terraform-locks-<env> with partition key LockID (String)backend.dev.hclbackend.stage.hclbackend.prod.hclUpdate bucket/table names if your naming differs.
cd docs/80_chain/templates/terraform/ecs-kafka-orchestrator
terraform init -reconfigure -backend-config=backend.dev.hcl
terraform plan -var-file=dev.tfvars
terraform init -reconfigure -backend-config=backend.stage.hcl
terraform plan -var-file=stage.tfvars
terraform init -reconfigure -backend-config=backend.prod.hcl
terraform plan -var-file=prod.tfvars
backend.<env>.hcl before plan/apply.