<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Terraform Cloud on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/terraform-cloud/</link><description>Recent content in Terraform Cloud on SRE Engineering Practice</description><image><title>SRE Engineering Practice</title><url>https://www.sre.wang/share-card-square.jpg</url><link>https://www.sre.wang/share-card-square.jpg</link></image><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 07 Oct 2026 01:11:40 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/terraform-cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>When Your Self-Hosted Terraform Backend Cracks at 30 Engineers: 6 Engineering Decisions and a TCO Ledger from Moving to HCP Terraform</title><link>https://www.sre.wang/en/posts/terraform-hcp-cloud-migration/</link><pubDate>Wed, 07 Oct 2026 01:11:40 +0800</pubDate><guid>https://www.sre.wang/en/posts/terraform-hcp-cloud-migration/</guid><description>After our team grew from 5 to 30 engineers, the self-hosted Terraform backend (S3 + lock table + hand-rolled CI scripts) started failing weekly: 17 state lock conflicts, two production environments broken by well-meaning manual applies, credentials leaking into CI logs. This is the decision log of our migration to HCP Terraform (formerly Terraform Cloud): six engineering decisions covering SaaS vs self-hosted platform selection, workspace organization, state migration pitfalls, Sentinel policy-as-code, CI/CD integration, and a real TCO ledger with an OpenTofu self-hosting comparison.</description></item></channel></rss>