ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #terraform
Learn how Terraform's for_each meta-argument lets you create multiple similar resources from a map or set, reducing duplication and giving precise control over each instance.
Learn how Terramate’s selective execution skips unchanged stacks in a monorepo, reducing plan/apply time and cost while keeping CI pipelines reliable.
Learn how to move infrastructure security and cost optimization from post-deployment audits to the pull request using Codeac's static analysis and cloud-resource detection.
Removing a list item with Terraform count can cause a cascade of destroy/recreate actions for all later instances. Using for_each keyed by a stable identifier avoids that by giving each instance a unique address.
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.
Use Terramate to turn a monorepo of Terraform root modules into independent, independently plannable stacks. Learn how to generate shared backends, detect changes via git, and run CI safely with minimal design and clear trust boundaries.
Learn the minimal, secure design for Terraform remote state locking using Amazon S3 and DynamoDB, including trust boundaries, operational checks, failure modes, and when to revisit the architecture.
Stop risking state corruption and security leaks. Learn how to migrate Terraform from local state to a remote S3 and DynamoDB backend for secure, team-based collaboration.
Step‑by‑step guide to enable Terraform state locking using an S3 backend and a DynamoDB lock table, including setup, verification, and recovery procedures.
dynamodb