Availability zones data source in Terraform - Mini Project: Build & Apply

Availability zones data source

📖 Scenario: You are setting up cloud infrastructure and need to find out which availability zones are available in your chosen region. This helps you plan where to deploy your resources for better reliability.

🎯 Goal: Use Terraform to fetch the list of availability zones in the current region and store them in a variable for later use.

📋 What You'll Learn

Use the aws_availability_zones data source to get availability zones

Create a variable called available_zones to store the list of zone names

💡 Why This Matters

🌍 Real World

Knowing available zones helps deploy resources in multiple places to avoid downtime.

💼 Career

Cloud engineers often need to query cloud provider data sources to automate infrastructure deployment.

1

Create AWS provider configuration

Write a Terraform block to configure the AWS provider with the region set to us-east-1.

Terraform

# Your code here

Hint

Use provider "aws" block and set region = "us-east-1".

2

Add data source for availability zones

Add a Terraform data block named aws_availability_zones with the name available to fetch availability zones in the current region.

Terraform

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

# Your code here

Hint

Use data "aws_availability_zones" "available" and set state = "available" to get only available zones.

3

Create a local variable for zone names

Create a locals block with a variable called available_zones that extracts the list of zone names from data.aws_availability_zones.available.names.

Terraform

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

data "aws_availability_zones" "available" {
  state = "available"
}

# Your code here

Hint

Use locals block and assign available_zones = data.aws_availability_zones.available.names.

4

Output the availability zones

Add an output block named zones that outputs the local.available_zones list.

Terraform

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

data "aws_availability_zones" "available" {
  state = "available"
}

locals {
  available_zones = data.aws_availability_zones.available.names
}

# Your code here

Hint

Use output "zones" block and set value = local.available_zones.

Practice

1. What is the main purpose of the availability_zones data source in Terraform?

easy

A. To delete unused availability zones

B. To create new availability zones in a region

C. To list all availability zones in a specified cloud region

D. To monitor the health status of availability zones

Solution

1. Step 1: Understand the data source role

   The availability_zones data source is used to fetch information, not to create or delete resources.

2. Step 2: Identify what information it provides

   It returns a list of availability zones available in the specified region, helping to distribute resources.

3. Final Answer:

   To list all availability zones in a specified cloud region -> Option C

4. Quick Check:

   Data source lists zones [OK]

Hint: Data sources fetch info; they don't create or delete [OK]

Common Mistakes:

• Thinking data source creates zones
• Confusing data source with resource
• Assuming it monitors zone health

2. Which of the following is the correct syntax to declare the AWS availability zones data source in Terraform?

easy

A. module "aws_availability_zones" {}

B. resource "aws_availability_zones" "example" {}

C. provider "aws_availability_zones" {}

D. data "aws_availability_zones" "example" {}

Solution

1. Step 1: Identify the correct Terraform block type for data sources

   Data sources use the data block, not resource, provider, or module.

2. Step 2: Check the correct resource type name

   The AWS availability zones data source is named aws_availability_zones, so the syntax is data "aws_availability_zones" "example" {}.

3. Final Answer:

   data "aws_availability_zones" "example" {} -> Option D

4. Quick Check:

   Data source syntax = data + resource type [OK]

Hint: Data sources start with 'data' keyword, not 'resource' [OK]

Common Mistakes:

• Using resource instead of data
• Using provider or module blocks incorrectly
• Misspelling the data source name

3. Given this Terraform snippet, what will output.zones contain?

data "aws_availability_zones" "available" {}

output "zones" {
  value = data.aws_availability_zones.available.names
}

medium

A. A list of availability zone names in the current AWS region

B. An error because names is not a valid attribute

C. A count of availability zones as a number

D. An empty list because no zones are specified

Solution

1. Step 1: Understand the data source attributes

   The aws_availability_zones data source provides an attribute names which is a list of zone names in the region.

2. Step 2: Check the output value

   The output references data.aws_availability_zones.available.names, so it will output the list of zone names.

3. Final Answer:

   A list of availability zone names in the current AWS region -> Option A

4. Quick Check:

   Output uses .names attribute = list of zones [OK]

Hint: Use .names to get zone names list from data source [OK]

Common Mistakes:

• Assuming .names attribute does not exist
• Expecting a count instead of list
• Thinking output is empty without explicit zones

4. You wrote this Terraform code but get an error: data.aws_availability_zones.invalid not found. What is the problem?

data "aws_availability_zones" "valid" {}

output "zones" {
  value = data.aws_availability_zones.invalid.names
}

medium

A. You must specify zones explicitly in the data source

B. The data source name used in output does not match the declared name

C. The names attribute does not exist

D. Terraform does not support availability zones data source

Solution

1. Step 1: Check the data source declaration

   The data source is declared as aws_availability_zones.valid.

2. Step 2: Check the output reference

   The output references data.aws_availability_zones.invalid, which does not exist.

3. Step 3: Identify the mismatch

   The error occurs because the output references a non-existent data source name.

4. Final Answer:

   The data source name used in output does not match the declared name -> Option B

5. Quick Check:

   Name mismatch causes not found error [OK]

Hint: Match data source names exactly in output references [OK]

Common Mistakes:

• Using wrong data source name in output
• Assuming .names attribute is missing
• Thinking zones must be specified manually

5. You want to deploy resources evenly across exactly 2 availability zones using Terraform's aws_availability_zones data source. Which code snippet correctly limits the zones to 2?

hard

A. data "aws_availability_zones" "example" {
state = "available"
filter {
name = "zone-name"
values = ["us-east-1a", "us-east-1b"]
}
}

B. data "aws_availability_zones" "example" {
state = "available"
all_availability_zones = false
filter {
name = "zone-name"
values = ["us-east-1a", "us-east-1b"]
}
}

C. data "aws_availability_zones" "example" {
state = "available"
all_availability_zones = true
filter {
name = "zone-name"
values = ["us-east-1a", "us-east-1b"]
}
}

D. data "aws_availability_zones" "example" {
state = "available"
zones = ["us-east-1a", "us-east-1b"]
}

Solution

1. Step 1: Understand filtering in aws_availability_zones

   The data source returns only AZs matching the filter criteria when a filter block is provided with name = "zone-name" and desired values.

2. Step 2: Identify valid configuration

   Use state = "available" and filter { name = "zone-name" values = ["us-east-1a", "us-east-1b"] } to limit exactly to those two zones.

3. Step 3: Invalid alternatives fail

   Using all_availability_zones or zones introduces non-existent arguments, causing Terraform validation errors.

4. Final Answer:

   data "aws_availability_zones" "example" { state = "available" filter { name = "zone-name" values = ["us-east-1a", "us-east-1b"] } } -> Option A

5. Quick Check:

   zone-name filter limits to specified AZs [OK]

Hint: Use zone-name filter to select specific AZs [OK]

Common Mistakes:

• Using invalid attributes like all_availability_zones
• Using unsupported 'zones' attribute
• Overcomplicating with non-existent parameters