In this issue of Mission Infrastructure, we explore what’s involved in provisioning and managing production infrastructure when you have more than one cloud provider. Multicloud infrastructure involves a lot of moving parts, but we help you to keep it all in line with a selection of insightful blog posts. Plus, we bring you recent videos, news of events we’ll be attending, and our latest product updates.
How do you provision and manage production infrastructure in more than one cloud provider? Mariusz Michalowski’s article explores pros, cons, and common misconceptions surrounding multicloud infrastructure. You’ll also learn about some good tools and processes for supporting infrastructure in multiple clouds.
Terraform multicloud provisioning is quite similar to Terraform single-cloud provisioning. It brings challenges and benefits and should not be adopted as a strategy without a solid business or technical use case. In this article, Mattias Fjellström discusses Terraform multicloud provisioning and outlines an example of a Terraform configuration that targets the three large cloud service providers: AWS, Azure, and Google Cloud.
Multicloud infrastructure improves resilience and flexibility at scale, but it raises unique challenges for DevOps processes. Read James Walker's article to learn about the effects of multicloud infrastructure on the DevOps lifecycle, its benefits and challenges, and best practices to follow when implementing multi-cloud DevOps workflows.
Kubernetes supports a multicloud architecture through the multiple cluster model, which involves deploying independent clusters in each cloud provider. In this article, James Walker outlines how to develop a multicloud, multi-cluster Kubernetes strategy, its benefits and challenges, recommended dedicated cluster administration tools, and best practices.
Although multicloud architecture enables more disaster recovery options by allowing you to fail over to a secondary cloud or restore a backup stored with another provider, multicloud disaster recovery can also increase operational complexity due to the number of components involved. In this article, James Walker discusses benefits, challenges, and best practices to consider when designing a multicloud disaster recovery strategy and outlines key steps for building reliable recovery processes that support business continuity during cloud outages.
Modern multicloud management is designed to give teams a consistent way to build and run across clouds and on-premises. In this guide, Mariusz Michalowski compares multicloud management platforms covering IaC pipelines, self-service catalogs, FinOps dashboards, and resilience tooling, so you can mix and match based on priorities and your existing stack.
Spacelift Intelligence is a new AI infrastructure suite that enables developers and AI agents to move faster, while platform and security teams maintain governance, visibility, and control.
In this session on Spacelift Intelligence and the dual-path deployment model, you'll learn about:
Combining IaC and GitOps workflows with AI-powered infrastructure deployment
Using an infrastructure assistant to understand, design, and troubleshoot infrastructure faster
Maintaining governance with policy as code, access controls, and full operational visibility across IaC and AI infrastructure deployments
Going to the AWS Summit in London this year? Spacelift is a Gold Sponsor, and we’d love to meet you! Drop by our booth to chat about how we can help you build collaborative, self-service infrastructure with a powerful AWS integration.
After the success of the inaugural IaCConf 2025, we can’t wait for IaCConf 2026! This free virtual event brings together DevOps professionals to discuss what really matters in the world of modern infrastructure. Hear real-world stories that will resonate and attend fascinating demos and panel discussions.
When you have multiple Terraform environments (think dev, test, UAT, staging, and prod), a single mistake can result in running a plan against the production state. The central issue is state separation, workflow safety, and human error. In this video, we examine practical ways to manage multiple Terraform environments efficiently, the requirements common to most teams (same IaC across environments, permanent non-prod that mirrors prod, ephemeral test environments, separation via accounts and credentials), and the trade-offs underlying four common approaches: Terraform CLI workspaces, Git branches per environment, Terragrunt, and Spacelift Stacks.
Because Terraform Cloud and Terraform Enterprise policies often surface violations late, governance can become a last-minute blocker, turning approvals into bottlenecks, exceptions into escalations, and delivery into a slow process. In this video, we look at the fundamental limitations of Terraform Cloud and Enterprise policy workflows, why late-stage enforcement causes friction, and why policy as code should progress work rather than block it at the final gate. We also demonstrate what built-in governance looks like when policies run throughout the workflow with early, actionable feedback.
“Infrastructure rarely breaks because of bad tools, it breaks because of untested assumptions. Subscribe to learn my hard-won lessons from scaling systems at Facebook and Google, the highs and lows of co-founding OpenTofu and Spacelift, and everything in between.”
Marcin Wyszynski, Co-founder @ Spacelift & OpenTofu
Spacelift Intelligence is a new set of AI capabilities built directly into the Spacelift platform. It comprises two components that work together: an embedded AI chat interface called Infra Assistant and a natural language deployment model called Intent. For more information, read this blog post. Also, make sure you sign up for the webinar we mentioned earlier, and see Spacelift Intelligence in action here.
No-op resources removed from plan policy payload
We’ve improved how plan policies are evaluated for Terraform, OpenTofu, and Terragrunt stacks. Unchanged resources will no longer be included in the policy input data when a plan is evaluated against your plan policies. This change will be invisible for most customers, and we will be reaching out directly to customers whose accounts could be affected.
