Availability zones data source in Terraform - Step-by-Step Execution

Process Flow - Availability zones data source

Start Terraform Plan

↓

Call data source: availability_zones

↓

Query cloud provider for AZs

↓

Receive list of AZs

↓

Store AZs in Terraform state

↓

Use AZs in resource definitions

↓

Apply infrastructure changes

Terraform queries the cloud provider for available zones, stores them, and uses them to deploy resources in those zones.

Execution Sample

Terraform

data "aws_availability_zones" "available" {}

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

This code fetches the list of AWS availability zones and outputs their names.

Process Table

Step	Action	Evaluation	Result
1	Start Terraform plan	Terraform begins execution	Ready to query data sources
2	Call data source aws_availability_zones	Request AZ list from AWS	AWS returns list of AZs
3	Store AZ list in state	Save AZ names in Terraform state	AZ names stored: ["us-east-1a", "us-east-1b", "us-east-1c"]
4	Output az_names	Read AZ names from data source	Output value: ["us-east-1a", "us-east-1b", "us-east-1c"]
5	End plan	All data sources resolved	Terraform ready to apply resources using AZs

💡 Terraform finishes data source query and stores AZs for resource use

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
data.aws_availability_zones.available.names	undefined	["us-east-1a", "us-east-1b", "us-east-1c"]	["us-east-1a", "us-east-1b", "us-east-1c"]	["us-east-1a", "us-east-1b", "us-east-1c"]

Key Moments - 3 Insights

Why does Terraform query availability zones before creating resources?

Terraform queries AZs first (see step 2 in execution_table) to know which zones exist so it can place resources correctly.

Can the list of availability zones change between runs?

Yes, the data source fetches live info each run (step 2), so if AWS adds or removes zones, Terraform sees the update.

What happens if the data source fails to get AZs?

Terraform plan will fail at step 2 because it cannot get required info, stopping deployment until fixed.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of data.aws_availability_zones.available.names after step 3?

A null

B undefined

C ["us-east-1a", "us-east-1b", "us-east-1c"]

D []

💡 Hint

Check variable_tracker column 'After Step 3' for data.aws_availability_zones.available.names

At which step does Terraform receive the list of availability zones from AWS?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

See execution_table row for Step 2 describing AWS response

If AWS adds a new availability zone, how will the execution_table change?

A Step 3 will store the new AZ in the list

B Step 1 will change

C Step 4 output will remain the same

D Terraform will skip querying AZs

💡 Hint

Look at how step 3 stores AZ names in variable_tracker

Concept Snapshot

Terraform availability zones data source:
- Use data "aws_availability_zones" to fetch AZs
- Terraform queries cloud provider live each run
- AZ names stored in state for resource use
- Helps deploy resources across zones
- Output AZ names with data source attribute

Full Transcript

This visual execution shows how Terraform uses the availability zones data source. First, Terraform starts the plan and calls the data source to query AWS for available zones. AWS returns the list of zones, which Terraform stores in its state. Then Terraform outputs the zone names. This process ensures Terraform knows which zones exist before creating resources. The variable tracking shows the AZ names are undefined at start and set after the query. Key moments clarify why Terraform queries AZs first and what happens if the query fails. The quiz tests understanding of when and how AZ names are retrieved and stored.

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