Infrastructure-as-code workflow template
The Terraform change workflow: branch, checks, plan on the PR, review, merge, apply with locked state, and drift detection.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- State & safety
- Remote state: S3 + DynamoDB lock (or Terraform Cloud) · One state per environment + component · Production apply needs 2 approvals · Modules versioned and pinned
Also on the board
- Change a Terraform module in a branch
- CI: fmt, validate, tflint, checkov
- terraform plan → posted on the PR
- Open a pull request
- Plan approved?
- terraform apply in CI (state locked)
- Nightly drift detection
- Update code, push again
- Merge to main
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Link by dragging. Hover a box and drag one of its dots onto another box. The whole box is the target, and links stay attached when you move things.
- Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
- Group by environment or region. Draw a frame (F) around a group of services; moving the frame moves everything inside it.
Good for
- terraform
- iac
- devops
- gitops
- cloud
- Design reviews and architecture decision meetings
- Runbooks and onboarding for on-call engineers
- Planning a migration or a cost-cutting pass
Related templates
Kubernetes cluster overview
Ingress, services, deployments and pods in a namespace, with config, storage, control plane and add-ons around them.
Cloud cost optimization board
FinOps actions sorted from quick wins to governance: clean up, right-size, commit, re-architect and keep costs visible.
GitOps workflow (Argo CD)
Deploy by pull request: CI builds the image, a config-repo PR bumps the tag, and Argo CD syncs the cluster to match git.
AWS three-tier web app
A highly available web app on AWS: DNS and CDN, load balancer, auto-scaled app servers and Multi-AZ database in a VPC.
CI/CD pipeline with quality gates
From pull request to production: build, tests, security scans, staging, approval and canary release, with the gates in between.
Canary & blue/green deployment
Release safely: shift a little traffic to the new version, check SLOs, then promote or roll back — plus a strategy comparison.