Resource arguments and attributes in Terraform - Mini Project: Build & Apply

Terraform Resource Arguments and Attributes

📖 Scenario: You are setting up a simple cloud infrastructure using Terraform. You want to create a virtual machine instance with specific settings and then access its attributes to use elsewhere in your configuration.

🎯 Goal: Build a Terraform configuration that defines a virtual machine resource with given arguments and then outputs one of its attributes.

📋 What You'll Learn

Create a resource block for an AWS EC2 instance named example.

Set the ami argument to "ami-0c55b159cbfafe1f0".

Set the instance_type argument to "t2.micro".

Create an output named instance_id that outputs the instance's ID attribute.

💡 Why This Matters

🌍 Real World

Terraform is widely used to automate cloud infrastructure setup. Defining resources with arguments and accessing their attributes is fundamental to managing cloud environments.

💼 Career

Cloud engineers and DevOps professionals use Terraform to create and manage infrastructure efficiently and reproducibly.

1

Create the AWS EC2 instance resource

Create a Terraform resource block named aws_instance with the resource name example. Set the ami argument to "ami-0c55b159cbfafe1f0" and the instance_type argument to "t2.micro".

Terraform

# Your code here

Hint

Use the resource keyword followed by the resource type aws_instance and the name example. Inside the block, set the ami and instance_type arguments exactly as specified.

2

Add a tag argument to the instance

Inside the aws_instance.example resource block, add a tags argument with a map containing Name = "ExampleInstance".

Terraform

resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  # Your code here
}

Hint

Use the tags argument with curly braces to define a map. Inside, set the key Name to the value "ExampleInstance".

3

Create an output for the instance ID

Create an output block named instance_id that outputs the attribute id of the resource aws_instance.example.

Terraform

resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "ExampleInstance"
  }
}

# Your code here

Hint

Use the output keyword with the name instance_id. Inside, set value to aws_instance.example.id to get the instance's ID.

4

Add a provider block for AWS

Add a provider block for aws with the region set to "us-east-1".

Terraform

# Your code here

resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "ExampleInstance"
  }
}

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

Hint

Use the provider block with the name aws. Inside, set the region argument to "us-east-1".

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