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.