ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terraform
Learn how to configure an S3 backend with DynamoDB locking to safely store Terraform state and prevent concurrent modifications.
Use Terramate stack dependencies and terramate run to execute Terraform commands across multiple stacks in the correct order.
Run terraform plan and apply only in stacks with modified files using terramate run --only-changed, reducing execution time and preventing unintended infrastructure changes.
Terramate adds a stack-and-blueprint orchestration layer above Terraform to eliminate copy-paste drift across accounts and regions. This post walks through a concrete VPC blueprint, generated HCL, and the run-time orchestration that keeps large fleets consistent.
Use a Terraform remote backend with state locking to prevent concurrent apply conflicts and share state safely across a team.
Use an S3 backend with a DynamoDB lock table so Terraform automatically serializes concurrent plan and apply operations.
Move Terraform state to a versioned S3 bucket and protect concurrent writes with a DynamoDB lock table. This guide covers backend configuration, init, verification checks, and recovery options.
Terraform's for_each meta-argument solves count's index-shift problem by addressing resources with stable keys. See a worked IAM example, targeting commands, and the plan-time trade-offs to watch.
Terramate streamlines Terraform by organizing code into stacks, generating reusable templates, and orchestrating incremental runs. This guide covers the minimal setup, trust boundaries, operational checks, failure modes, and when to evolve the architecture.
dynamodb