Resource arguments and attributes in Terraform - Commands & Configuration

Introduction

When you create infrastructure with Terraform, you tell it what you want using resource arguments. After creation, Terraform gives you resource attributes that show details about what was made. This helps you manage and connect your cloud resources easily.

When you want to create a virtual machine with specific settings like size and region.

When you need to set up a storage bucket and want to know its URL after creation.

When you want to connect one resource to another using information Terraform provides after deployment.

When you want to customize a resource by giving it names, tags, or other options.

When you want to check the current state or properties of a resource after Terraform applies changes.

Config File - main.tf

main.tf

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 4.0"
    }
  }
  required_version = ">= 1.0"
}

provider "aws" {
  region = "us-east-1"
}

resource "aws_s3_bucket" "example_bucket" {
  bucket = "my-example-bucket-terraform-12345"
  acl    = "private"
  tags = {
    Environment = "Dev"
    Project     = "TerraformDemo"
  }
}

output "bucket_arn" {
  value = aws_s3_bucket.example_bucket.arn
}

This Terraform file sets up the AWS provider to work in the us-east-1 region.

The aws_s3_bucket resource creates a private S3 bucket with a specific name and tags.

The bucket and acl are resource arguments that tell Terraform what to create.

The output block shows the bucket's ARN attribute after creation, which is useful for connecting or referencing this bucket elsewhere.

Commands

This command sets up Terraform in the current folder by downloading the AWS provider plugin. It prepares Terraform to create resources.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding hashicorp/aws versions matching "~> 4.0"...

- Installing hashicorp/aws v4.60.0...

- Installed hashicorp/aws v4.60.0 (signed by HashiCorp)



Terraform has been successfully initialized!



You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure.

This command shows what Terraform will do before making any changes. It uses the resource arguments to plan creating the S3 bucket.

Terminal

terraform plan

Expected Output

An execution plan has been generated and is shown below.

Resource actions are indicated with the following symbols:

  + create



Terraform will perform the following actions:



  # aws_s3_bucket.example_bucket will be created

  + resource "aws_s3_bucket" "example_bucket" {

      + acl                         = "private"

      + arn                         = (known after apply)

      + bucket                      = "my-example-bucket-terraform-12345"

      + id                          = (known after apply)

      + tags                        = {

          + "Environment" = "Dev"

          + "Project"     = "TerraformDemo"

        }

    }



Plan: 1 to add, 0 to change, 0 to destroy.

This command creates the S3 bucket using the arguments defined. The -auto-approve flag skips asking for confirmation.

Terminal

terraform apply -auto-approve

Expected Output

aws_s3_bucket.example_bucket: Creating...

aws_s3_bucket.example_bucket: Creation complete after 3s [id=my-example-bucket-terraform-12345]



Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

→

-auto-approve - Automatically approve the apply without asking for confirmation

This command shows the ARN attribute of the created S3 bucket. It helps you see details Terraform knows after creation.

Terminal

terraform output bucket_arn

Expected Output

arn:aws:s3:::my-example-bucket-terraform-12345

Key Concept

If you remember nothing else from this pattern, remember: resource arguments tell Terraform what to create, and resource attributes show details about what was created.

Common Mistakes

Using resource attributes as arguments inside the same resource block.

Terraform cannot use attributes that only exist after creation as input arguments during creation.

Use resource arguments to define what you want, and access attributes only after the resource is created or in other resources.

Not running 'terraform init' before 'terraform plan' or 'apply'.

Terraform needs to download provider plugins before it can work, so commands fail without initialization.

Always run 'terraform init' first in a new Terraform project folder.

Summary

Use resource arguments in Terraform files to specify the settings for the infrastructure you want to create.

Run 'terraform init' to prepare Terraform, then 'terraform plan' to see what will happen.

Run 'terraform apply' to create resources, then use 'terraform output' to see resource attributes.

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