<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud-Kms on RLGeeX</title><link>https://www.rlgeex.com/tags/cloud-kms/</link><description>Recent content in Cloud-Kms on RLGeeX</description><generator>Hugo</generator><language>en-us</language><copyright>RLGeeX © 2025 - Real-Life Geeks providing expert IT consulting</copyright><lastBuildDate>Thu, 05 Feb 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://www.rlgeex.com/tags/cloud-kms/index.xml" rel="self" type="application/rss+xml"/><item><title>Terraform State on GCS: Treat the Bucket as Foundation Infrastructure</title><link>https://www.rlgeex.com/news/terraform-state-on-gcs-treat-the-bucket-as-foundation-infrastructure/</link><pubDate>Thu, 05 Feb 2026 09:00:00 -0500</pubDate><guid>https://www.rlgeex.com/news/terraform-state-on-gcs-treat-the-bucket-as-foundation-infrastructure/</guid><description>&lt;p>This post is for cloud engineers building a GCP foundation with Terraform. You will get a short, opinionated setup for keeping state in Cloud Storage. My argument is that the state bucket is foundation infrastructure in its own right. Create it first, guard it like production, and choose its encryption knowing which choices are hard to undo. The &lt;code>backend &amp;quot;gcs&amp;quot;&lt;/code> block itself is the easy part.&lt;/p>
&lt;h2 id="why-state-leaves-your-laptop">Why state leaves your laptop&lt;a href="#why-state-leaves-your-laptop" class="anchor" aria-hidden="true">&lt;svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
 stroke-linecap="round" stroke-linejoin="round">
 &lt;path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3">&lt;/path>
 &lt;line x1="8" y1="12" x2="16" y2="12">&lt;/line>
 &lt;/svg>&lt;/a>&lt;/h2>
&lt;p>By default, Terraform keeps state locally in a file named &lt;code>terraform.tfstate&lt;/code>. Google&amp;rsquo;s tutorial on &lt;a href="https://docs.cloud.google.com/docs/terraform/resource-management/store-state">storing Terraform state in a Cloud Storage bucket&lt;/a> points out that this makes team use difficult when several people run Terraform at the same time, because each machine has its own picture of the infrastructure. A foundation is shared by definition, with an org, folders, networking and IAM that many people depend on. For a foundation, remote state is required from the first apply.&lt;/p></description></item></channel></rss>