Common Data Source Patterns
What you'll learn: How to leverage data sources to query existing cloud resources like AMIs, availability zones, VPCs, and more in your Terraform configurations.
Why Query Existing Resources?
You've learned that data sources let you read information from your cloud provider. Now let's explore the most common patterns you'll use daily. Think of data sources as reference lookups—instead of hardcoding an AMI ID or guessing availability zone names, you query them dynamically.
Common Patterns You'll Use
Querying Amazon Machine Images (AMIs): Use filters to find the latest AMI matching specific criteria, like operating system or owner.
data "aws_ami" "ubuntu_latest" {
most_recent = true
owners = ["099720109477"]
filter {
name = "name"
values = ["ubuntu/images/hbf-ssd/ubuntu-focal-20.04-amd64-server-*"]
}
}
Listing Availability Zones: Dynamically discover which zones are available in your region.
data "aws_availability_zones" "available" {
state = "available"
}
Finding Existing VPCs: Reference a VPC created outside Terraform or in another configuration.
data "aws_vpc" "main" {
default = true
}
Why This Matters
These patterns prevent brittle configurations. Instead of hardcoding ami-12345, you query "the latest Ubuntu AMI," ensuring your infrastructure stays current. Instead of listing specific zones, you discover them dynamically, making your code portable across regions.
Key Takeaway: Common data source patterns—querying AMIs, availability zones, VPCs, and existing resources—make your Terraform configurations dynamic, portable, and maintainable by eliminating hardcoded values.