DevOps Bootcamp · Lesson

Multi-Cloud and Hybrid Cloud Patterns

Design and implement Terraform configurations that span multiple cloud providers or integrate with on-premises infrastructure.

Multi-Cloud and Hybrid Cloud Patterns is a free DevOps Bootcamp lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the DevOps Bootcamp learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

What are Multi-Cloud & Hybrid?

Welcome to advanced Terraform patterns! In this lesson, we'll explore Multi-Cloud and Hybrid Cloud strategies.

Multi-Cloud: Using services from more than one public cloud provider (e.g., AWS, Azure, GCP) simultaneously.
Hybrid Cloud: Combining public cloud services with private infrastructure, such as your on-premises data center.

Both patterns aim to leverage the best of different environments.

Why Use Multi-Cloud/Hybrid?

These advanced patterns offer significant benefits for modern infrastructure:

Avoid Vendor Lock-in: Reduces reliance on a single cloud provider.
Enhanced Resilience: Distribute workloads across clouds to improve disaster recovery.
Cost Optimization: Choose the most cost-effective provider for specific services.
Compliance & Data Sovereignty: Meet regulatory requirements by keeping data in specific regions or on-premises.
Leverage Best-of-Breed: Utilize unique services from different providers.

Terraform's Role in Unification

Managing resources across disparate environments can be complex. This is where Terraform shines!

Terraform provides a consistent workflow to provision and manage infrastructure from multiple cloud providers and even on-premises systems, all from a single codebase. It acts as a universal language for your entire infrastructure landscape.

Configuring Multiple Providers

To work with different clouds, you declare multiple provider blocks in your Terraform configuration. Each block specifies a cloud provider and its configuration details.

Here's how you might set up both AWS and Azure providers in one file:

provider "aws" {
  region = "us-east-1"
}

provider "azurerm" {
  features {}
  region = "eastus"
}

Deploying Multi-Cloud Resources

Once providers are configured, you can define resources for each cloud within the same `.tf` file. Terraform knows which provider to use based on the resource type prefix (e.g., aws_s3_bucket vs. azurerm_resource_group).

Try running this example:

provider "aws" {
  region = "us-east-1"
}

provider "azurerm" {
  features {}
  region = "eastus"
}

resource "aws_s3_bucket" "my_multi_cloud_bucket" {
  bucket = "my-unique-multi-cloud-bucket-12345"
}

resource "azurerm_resource_group" "my_multi_cloud_rg" {
  name     = "MultiCloudResourceGroup"
  location = "eastus"
}

Cross-Cloud Resource Referencing

A powerful multi-cloud pattern is sharing information between resources deployed in different clouds. You can use output values from one cloud's resources as input for another.

For example, you could output an S3 bucket name from AWS and use it in an Azure resource's tag or configuration.

provider "aws" {
  region = "us-east-1"
}

provider "azurerm" {
  features {}
  region = "eastus"
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = "cross-cloud-example-bucket-12345"
}

output "aws_bucket_name" {
  value = aws_s3_bucket.my_bucket.bucket
}

resource "azurerm_resource_group" "my_rg" {
  name     = "CrossCloudRG"
  location = "eastus"
  tags = {
    "SourceBucket" = aws_s3_bucket.my_bucket.bucket
  }
}

Hybrid Cloud: On-Prem Integration

Hybrid cloud involves connecting your cloud environment with your on-premises data center. Terraform helps by configuring the cloud-side of this connection.

VPN Gateways: Terraform can provision cloud VPN gateways (e.g., AWS Site-to-Site VPN, Azure VPN Gateway).
Direct Connect/ExpressRoute: While physical connections are manual, Terraform can configure the virtual interfaces and associated networking on the cloud side.

Hybrid Cloud: Data from On-Prem

To truly integrate, Terraform might need information from your on-premises systems. This can be achieved using Data Sources.

external data source: Runs a local command/script to fetch data (e.g., from an on-prem API, database, or inventory system) and makes it available to Terraform.
Custom Providers: For deeper integration, a custom Terraform provider can be built to interact directly with on-premises APIs or systems.

Best Practices for Multi-Cloud

Managing multi-cloud or hybrid environments effectively requires good practices:

Modularity: Use Terraform modules to encapsulate cloud-specific configurations.
Consistent Naming: Establish a clear naming convention across all environments.
Remote State: Use remote state backends (e.g., S3, Azure Blob Storage) for collaborative and secure state management.
Separate Workspaces: Use workspaces or separate directories for different environments (dev, staging, prod) within each cloud.
Policy as Code: Implement policies (e.g., Sentinel) to enforce governance across clouds.

Multi-Cloud Challenge

Which of the following are valid reasons to adopt a Multi-Cloud strategy with Terraform?

Multi-Cloud & Hybrid Recap

Great job! You've learned about advanced Terraform patterns for Multi-Cloud and Hybrid Cloud environments.

Terraform allows you to manage resources across different public clouds and integrate with on-premises infrastructure.
Key benefits include avoiding vendor lock-in, improving resilience, and optimizing costs.
You configure multiple provider blocks and can even reference resources across clouds.
Best practices like modularity and remote state are crucial for managing complexity.

Next, we'll explore policy-as-code for governance.

Frequently asked questions

Is the “Multi-Cloud and Hybrid Cloud Patterns” lesson free?

Yes — the full text of “Multi-Cloud and Hybrid Cloud Patterns” is free to read here on the web, and the DevOps Bootcamp course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the DevOps Bootcamp course, upgrade to CoddyKit PRO.

What will I learn in “Multi-Cloud and Hybrid Cloud Patterns”?

Design and implement Terraform configurations that span multiple cloud providers or integrate with on-premises infrastructure. You practise DevOps Bootcamp with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start DevOps Bootcamp?

No prior experience is required. DevOps Bootcamp on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Multi-Cloud and Hybrid Cloud Patterns” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this DevOps Bootcamp lesson?

Yes. Every DevOps Bootcamp lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to DevOps Bootcamp