ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Architecture note on using an S3 backend with native lockfile for Terraform state, covering requirements, trust boundaries, operational checks, failure modes, and when to reconsider the design.
When Terraform blocks on a state lock, the culprit is often a missing DynamoDB table, bad IAM rights, or stale lock items. This guide walks through the most common symptoms, ordered checks, and step‑by‑step fixes so you can restore normal operation quickly.
The goal is to understand how Terramate’s orchestration layer interacts with Terraform’s native state‑locking mechanism when managing nested stacks. Terramate generates HCL and orders execution based on a dependency graph, but it does not provide its own lock; each Terraform invocation relies on the configured backend to acquire a lock on the state file. In
Terraform utilizes state locking in remote backends, such as S3 with DynamoDB, to prevent concurrent modifications that could lead to state corruption. When a process terminates unexpectedly or a network partition occurs between the client and the lock provider, a "ghost lock" may persist in the backend despite no active operation. The terraform force-unlock
terraform
dynamodb