<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infrastructure on FlowChassis.com</title>
    <link>https://flowchassis.com/tags/infrastructure/</link>
    <description>Recent content in Infrastructure on FlowChassis.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flowchassis.com/tags/infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cloud Provisioning With FlowChassis Tears Down What a Failed Deploy Built</title>
      <link>https://flowchassis.com/cloud-provisioning-with-flowchassis-tears-down-what-a-failed-deploy-built/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://flowchassis.com/cloud-provisioning-with-flowchassis-tears-down-what-a-failed-deploy-built/</guid>
      <description>&lt;p&gt;Putting a site on a new server takes a handful of calls to different providers. Create the VM. Point a DNS record at it. Get a TLS certificate. Then wait until the thing answers its health check, which can take a while because VMs take time to boot.&lt;/p&gt;&#xA;&lt;p&gt;When the certificate step fails, you&amp;rsquo;re left with a VM you pay for by the hour and a DNS record pointing at it. Run that a few hundred times across a team and you get the cloud bill everyone recognises: servers nobody remembers creating.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
