Resource arguments and attributes in Terraform - Step-by-Step Execution

Process Flow - Resource arguments and attributes

Define Resource Block

↓

Set Arguments (input values)

↓

Terraform Processes Resource

↓

Resource Created in Cloud

↓

Terraform Reads Attributes (output values)

↓

Use Attributes in Config or Output

Terraform resource blocks take arguments as input to create cloud resources, then provide attributes as output to use elsewhere.

Execution Sample

Terraform

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

output "instance_id" {
  value = aws_instance.example.id
}

Defines an AWS instance with arguments, then outputs its ID attribute after creation.

Process Table

Step	Action	Arguments Set	Resource State	Attributes Available
1	Start resource block	None yet	Not created	None
2	Set ami argument	ami = "ami-123456"	Not created	None
3	Set instance_type argument	instance_type = "t2.micro"	Not created	None
4	Terraform creates instance	ami and instance_type set	Instance created in AWS	id, arn, public_ip, etc.
5	Read attribute aws_instance.example.id	Arguments unchanged	Instance exists	id = "i-0abcd1234efgh5678"
6	Output instance_id value	Arguments unchanged	Instance exists	Output = "i-0abcd1234efgh5678"
7	End	No changes	Instance exists	Attributes stable

💡 Resource created and attributes read; output shows instance ID.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
ami	None	"ami-123456"	"ami-123456"	"ami-123456"	"ami-123456"	"ami-123456"
instance_type	None	None	"t2.micro"	"t2.micro"	"t2.micro"	"t2.micro"
resource_state	Not created	Not created	Not created	Created	Created	Created
id (attribute)	None	None	None	Available	"i-0abcd1234efgh5678"	"i-0abcd1234efgh5678"
output instance_id	None	None	None	None	None	"i-0abcd1234efgh5678"

Key Moments - 3 Insights

Why can't we use resource attributes before the resource is created?

Attributes like 'id' are only known after Terraform creates the resource (see step 4 and 5 in execution_table). Before creation, attributes are not available.

Are resource arguments and attributes the same thing?

No. Arguments are inputs you set to create the resource (steps 2 and 3). Attributes are outputs Terraform reads after creation (steps 5 and 6).

Can attributes be used in other resource blocks?

Yes. Attributes like 'id' can be referenced in other resources or outputs after creation, enabling dependencies and dynamic configs.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Terraform create the actual cloud resource?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Check the 'Resource State' column for when it changes to 'Instance created in AWS'.

According to variable_tracker, what is the value of 'id' attribute after step 5?

A "i-0abcd1234efgh5678"

B None

C "ami-123456"

D "t2.micro"

💡 Hint

Look at the 'id (attribute)' row under 'After Step 5' column.

If you change the 'instance_type' argument to 't3.small', which step in execution_table would reflect this change?

A Step 5

B Step 4

C Step 3

D Step 6

💡 Hint

Arguments are set before resource creation; see 'Arguments Set' column.

Concept Snapshot

Terraform resource blocks use arguments as inputs to create cloud resources.
After creation, Terraform provides attributes as outputs.
Arguments define what the resource should be.
Attributes give details about the created resource.
Attributes can be used in outputs or other resources.
Resource creation happens after all arguments are set.

Full Transcript

In Terraform, you define resources using blocks that include arguments. These arguments are like instructions telling Terraform what to create, such as the AMI ID and instance type for an AWS instance. Terraform processes these arguments and creates the resource in the cloud. Once created, Terraform reads attributes from the resource, like its unique ID, which you can use elsewhere in your configuration or outputs. The execution flow starts with setting arguments, then creating the resource, and finally reading attributes. Attributes are not available before creation. This process allows you to manage cloud resources declaratively and use their details dynamically.

Practice

1. In Terraform, what is the main purpose of resource arguments inside a resource block?

easy

A. To delete the resource from the cloud provider

B. To display information about the resource after creation

C. To output the resource's ID automatically

D. To specify the settings needed to create the resource

Solution

1. Step 1: Understand resource arguments

   Resource arguments define the configuration details needed to create the resource, like size or name.

2. Step 2: Differentiate arguments from attributes

   Attributes provide info after creation, but arguments tell Terraform what to build.

3. Final Answer:

   To specify the settings needed to create the resource -> Option D

4. Quick Check:

   Arguments configure resources = C [OK]

Hint: Arguments set resource details; attributes show info after creation [OK]

Common Mistakes:

• Confusing arguments with attributes
• Thinking arguments output resource info
• Assuming arguments delete resources

2. Which of the following is the correct syntax to define a resource argument in Terraform?

easy

A. resource "aws_instance" "example" { name = "my-instance" }

B. resource aws_instance example { name: "my-instance" }

C. resource "aws_instance" "example" (name = "my-instance")

D. resource "aws_instance" "example" [name = "my-instance"]

Solution

1. Step 1: Review Terraform resource block syntax

   Terraform uses curly braces {} to define resource arguments inside a resource block.

2. Step 2: Check correct key-value assignment

   Arguments use equals sign (=) with quoted strings for values inside the braces.

3. Final Answer:

   resource "aws_instance" "example" { name = "my-instance" } -> Option A

4. Quick Check:

   Curly braces and = sign = A [OK]

Hint: Use braces {} and = for arguments in resource blocks [OK]

Common Mistakes:

• Using parentheses or brackets instead of braces
• Using colon (:) instead of equals (=)
• Omitting quotes around strings

3. Given this Terraform resource snippet:

resource "aws_instance" "web" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

output "instance_id" {
  value = aws_instance.web.id
}

What will the output value show after deployment?

medium

A. The instance type of the created instance

B. The unique ID assigned to the created instance

C. The AMI ID used to create the instance

D. An error because output cannot access resource attributes

Solution

1. Step 1: Identify the output value expression

   The output uses aws_instance.web.id which is the attribute for the instance's unique ID.

2. Step 2: Understand resource attributes

   Attributes like id provide info about the created resource, here the instance ID.

3. Final Answer:

   The unique ID assigned to the created instance -> Option B

4. Quick Check:

   Output shows resource attribute id = A [OK]

Hint: Output value = resource.attribute (id is unique ID) [OK]

Common Mistakes:

• Confusing arguments with attributes
• Thinking output shows argument values
• Assuming output cannot access resource attributes

4. You wrote this Terraform resource:

resource "aws_s3_bucket" "mybucket" {
  bucket = my-bucket-name
  acl    = "private"
}

Terraform plan fails with an error. What is the problem?

medium

A. The bucket name must be in quotes as a string

B. The acl argument is invalid for S3 buckets

C. Resource type aws_s3_bucket is incorrect

D. Missing required provider block

Solution

1. Step 1: Check argument value types

   The bucket argument value my-bucket-name is not quoted, so Terraform treats it as a variable or error.

2. Step 2: Confirm correct string syntax

   Bucket names must be strings, so they need quotes like "my-bucket-name".

3. Final Answer:

   The bucket name must be in quotes as a string -> Option A

4. Quick Check:

   String values need quotes = D [OK]

Hint: Always quote string argument values in resource blocks [OK]

Common Mistakes:

• Forgetting quotes around string values
• Assuming acl is invalid for S3 buckets
• Thinking provider block is always required in snippet

5. You want to create multiple AWS EC2 instances with different names and instance types using a single resource block. Which Terraform feature lets you define arguments dynamically for each instance?

hard

A. Defining multiple resource blocks manually

B. Using output blocks to set arguments

C. Using resource count with indexed arguments

D. Using provider alias for each instance

Solution

1. Step 1: Understand dynamic resource creation

   Terraform's count argument allows creating multiple instances of a resource with indexed arguments.

2. Step 2: Apply count with argument interpolation

   You can use count.index to assign different names and types dynamically in one resource block.

3. Final Answer:

   Using resource count with indexed arguments -> Option C

4. Quick Check:

   Count enables multiple dynamic resources = B [OK]

Hint: Use count and count.index to create multiple resources dynamically [OK]

Common Mistakes:

• Manually duplicating resource blocks instead of using count
• Trying to set arguments via outputs
• Misusing provider aliases for resource count