From vibe coding to agentic workflows, AI has become unavoidable in infrastructure. In this edition of Mission Infrastructure, we bring you expert insights on the workflow guardrails that will free you to enjoy the speed gains that AI enables.
You will also find popular recent articles on everything from IaC adoption to multicloud compliance. And if you’re a new platform engineering head, don’t miss our 30-60-90 day plan. Plus, we've got news of interesting events and product updates.
New Articles — Top Picks
Guardrails for AI-Generated Infrastructure
The Spacelift 2026 Infrastructure Automation Report reveals that AI-caused infrastructure incidents have affected 93% of organizations, so teams leveraging AI for the genuine speed gains it delivers must learn how to do so safely. In this article, Ioannis Moustakis explores why AI workflows need guardrails and outlines a lifecycle model for applying them, from code generation to post-apply operations.
If you automate pipelines with a generalized automation tool that enables you to build your own automation workflows, you are likely to use a version control and collaboration platform such as GitHub, GitLab, or Bitbucket. In this article, Mattias Fjellström outlines how to configure Bitbucket Pipelines to securely provision infrastructure on the AWS platform.
IaC Adoption Strategy: How to Implement Infrastructure as Code
Tools such as Terraform, Pulumi, and OpenTofu underpin IaC, but successful adoption requires operating your tools efficiently and embedding them in your team’s working habits. In this article, James Walker explores the challenges that block IaC adoption, outlines a ten-step roadmap, and lists best practices to maintain IaC successfully.
Multicloud Compliance: Frameworks, Controls, and Evidence
Multicloud compliance involves meeting your regulatory, security, and governance requirements consistently across multiple cloud providers and proving that you do. James Walker’s article covers which regulations and standards apply to multicloud environments, why using more than one cloud provider makes compliance harder, the errors that cause compliance failures, how to craft a compliance strategy that scales, how to produce acceptable audit evidence, and which tools manage each layer.
Terraform providers are plugins that enable Terraform to interact with external APIs and provision the resources that comprise your application and system infrastructure. As with any versioned dependency for another configuration or programming language, you must manage the provider versions that your Terraform configuration uses. Mattias Fjellström’s article explains how to manage Terraform provider upgrades for your Terraform configurations and modules.
Join PayFit’s Adrien Stefanski, Staff Platform Engineer, and Tom Masson, Senior Platform, as they share how they brought Lambda into their standardized deployment platform. You’ll discover:
How they unified promotion workflows across Kubernetes and AWS Lambda
Why combining infrastructure and application changes improves release confidence
Lessons learned building a consistent deployment model across every workload
Gather practical insights for building a more consistent, reliable, and integrated delivery pipeline.
Relax after a packed day at LeadDev NYC with an evening of ping pong, tasty bites, and great company. Show off your backhand slice, share stories with scaling engineering teams, and enjoy refreshments with fellow engineering leaders, CTOs, and dev community peers.
30-60-90 Day Plan for New Heads of Platform Engineering
When you take over platform engineering, you’re unlikely to have any handover doc, playbook, or obvious first steps. In this video, we walk through what your first 30, 60, and 90 days as head of platform engineering should look like. The first month is about listening and understanding how the company actually works, the second is about finding the bottleneck and writing a technical vision, and the third is about becoming data-driven so you stop relying on opinions and goodwill.
You now land on the new Infra Assistant page by default when you open Spacelift. Infra Assistant has moved up in the main navigation and opens directly into that page now. Other changes include controls adapting to your screen size, chat history living in a side panel instead of a dropdown on wide screens, and refreshes of the quick-command examples.
Spacelift Notification Policies now reach Slack and GitHub
Connect your Slack or GitHub account under Personal Settings → External Accounts and link it to your Spacelift identity. Once it's authorized, Notification Policies can send updates straight to your linked account.
Historically, when something fails in our infrastructure, our API still responds with HTTP 200. The response body says "internal error," but the status code says everything was fine. Any monitoring tool watching status codes never sees the failure at all.Internal errors will soon return HTTP 500. Nothing about the failure itself will change, just the status code.
