Terraformcloud~30 mins

Zero-downtime deployment pattern in Terraform - Mini Project: Build & Apply

Choose your learning style10 modes available

Learn Why Deep Visual Try Challenge Project Recall Time

Start learning this pattern below

Jump into concepts and practice - no test required

Recommended

Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong

Zero-downtime deployment pattern

📖 Scenario: You are managing a web application hosted on a cloud provider. To avoid downtime during updates, you want to deploy a new version of your application alongside the old one, then switch traffic to the new version only after it is ready.

🎯 Goal: Build a Terraform configuration that creates two identical instances of a web server behind a load balancer. The load balancer should route traffic only to the active instance. You will configure the infrastructure to allow switching traffic from the old instance to the new instance without downtime.

📋 What You'll Learn

Create two compute instances with the same configuration but different names

Create a load balancer with a target group

Attach only one instance to the load balancer target group at a time

Add a variable to select which instance is active

Use the variable to control which instance receives traffic

💡 Why This Matters

🌍 Real World

Zero-downtime deployment is critical for web applications that must remain available during updates. This pattern is used in production environments to avoid service interruptions.

💼 Career

Cloud engineers and DevOps professionals use zero-downtime deployment patterns to ensure high availability and reliability of applications during updates.

Progress0 / 4 steps

Create two compute instances

Create two AWS EC2 instances named app_instance_old and app_instance_new with the AMI ID ami-0c55b159cbfafe1f0 and instance type t2.micro.

Terraform

# Your code here

Hint

Use two aws_instance resources with the specified AMI and instance type. Name them exactly app_instance_old and app_instance_new.

Create a load balancer and target group

Add an AWS Application Load Balancer resource named app_lb and a target group named app_tg with port 80 and protocol HTTP.

Terraform

resource "aws_instance" "app_instance_old" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "app_instance_old"
  }
}

resource "aws_instance" "app_instance_new" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "app_instance_new"
  }
}

# Your code here

Hint

Use aws_lb for the load balancer and aws_lb_target_group for the target group. Use port 80 and HTTP protocol.

Note: Replace subnet and VPC IDs with your actual values.

Add a variable to select the active instance

Create a Terraform variable named active_instance of type string with default value "old" to select which instance receives traffic.

Terraform

resource "aws_instance" "app_instance_old" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "app_instance_old"
  }
}

resource "aws_instance" "app_instance_new" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "app_instance_new"
  }
}

resource "aws_lb" "app_lb" {
  name               = "app-lb"
  internal           = false
  load_balancer_type = "application"
  subnets            = ["subnet-12345678", "subnet-87654321"]
}

resource "aws_lb_target_group" "app_tg" {
  name     = "app-tg"
  port     = 80
  protocol = "HTTP"
  vpc_id   = "vpc-12345678"
}

# Your code here

Hint

Define a variable block named active_instance with type string and default value "old".

Attach only the active instance to the target group

Create an aws_lb_target_group_attachment resource named active_attachment that attaches the instance selected by var.active_instance to the target group aws_lb_target_group.app_tg. Use a conditional expression to select aws_instance.app_instance_old.id if var.active_instance is "old", else aws_instance.app_instance_new.id.

Terraform

variable "active_instance" {
  type    = string
  default = "old"
}

resource "aws_instance" "app_instance_old" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "app_instance_old"
  }
}

resource "aws_instance" "app_instance_new" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "app_instance_new"
  }
}

resource "aws_lb" "app_lb" {
  name               = "app-lb"
  internal           = false
  load_balancer_type = "application"
  subnets            = ["subnet-12345678", "subnet-87654321"]
}

resource "aws_lb_target_group" "app_tg" {
  name     = "app-tg"
  port     = 80
  protocol = "HTTP"
  vpc_id   = "vpc-12345678"
}

# Your code here

Hint

Use a conditional expression for target_id to select the instance ID based on var.active_instance.

Practice

(1/5)

1. What is the main goal of a zero-downtime deployment in Terraform?

easy

A. Manually switch traffic after deployment

B. Update applications without stopping them or causing downtime

C. Deploy new versions only during off-hours

D. Stop all running tasks before updating

Zero-downtime deployment pattern in Terraform - Mini Project: Build & Apply

Start learning this pattern below

Practice

Solution

Step 1: Understand zero-downtime deployment purpose

Step 2: Compare options with this goal

Final Answer:

Quick Check:

Solution

Step 1: Identify settings related to task counts during update

Step 2: Understand min_healthy_percent role

Final Answer:

Quick Check:

Solution

Step 1: Interpret deployment_minimum_healthy_percent

Step 2: Interpret deployment_maximum_percent

Final Answer:

Quick Check:

Solution

Step 1: Analyze min and max percent both at 100%

Step 2: Understand deployment impact

Final Answer:

Quick Check:

Solution

Step 1: Evaluate each option for zero-downtime support

Step 2: Choose best balance for zero-downtime

Final Answer:

Quick Check: