Resource types and names in Terraform - Mini Project: Build & Apply

Terraform Resource Types and Names

📖 Scenario: You are setting up a simple cloud infrastructure using Terraform. You need to define resources with correct types and names to create a virtual machine and a storage bucket.

🎯 Goal: Build a Terraform configuration that defines an aws_instance resource named web_server and an aws_s3_bucket resource named app_bucket.

📋 What You'll Learn

Create an aws_instance resource with the name web_server.

Create an aws_s3_bucket resource with the name app_bucket.

Use valid Terraform syntax for resource blocks.

Use the exact resource types and names as specified.

💡 Why This Matters

🌍 Real World

Terraform is widely used to automate cloud infrastructure setup. Defining resources with correct types and names is the first step to managing cloud services like virtual machines and storage.

💼 Career

Cloud engineers and DevOps professionals use Terraform daily to create and maintain infrastructure as code, ensuring consistent and repeatable deployments.

1

Create an AWS instance resource

Create a Terraform resource block for an AWS instance with the resource type aws_instance and the resource name web_server. Set the ami attribute to "ami-12345678" and the instance_type attribute to "t2.micro".

Terraform

# Your code here to create aws_instance resource named web_server

Hint

Use the resource keyword, then the resource type aws_instance, followed by the resource name web_server in quotes.

2

Create an S3 bucket resource

Add a Terraform resource block for an AWS S3 bucket with the resource type aws_s3_bucket and the resource name app_bucket. Set the bucket attribute to "my-app-bucket".

Terraform

resource "aws_instance" "web_server" {
  ami           = "ami-12345678"
  instance_type = "t2.micro"
}

# Your code here to create aws_s3_bucket resource named app_bucket

Hint

Use the resource keyword with type aws_s3_bucket and name app_bucket. Set the bucket attribute inside.

3

Add tags to the AWS instance

Inside the aws_instance resource named web_server, add a tags block with a tag Name set to "WebServerInstance".

Terraform

resource "aws_instance" "web_server" {
  ami           = "ami-12345678"
  instance_type = "t2.micro"
  # Your code here to add tags block
}

resource "aws_s3_bucket" "app_bucket" {
  bucket = "my-app-bucket"
}

Hint

Use a tags block with key-value pairs inside the aws_instance resource.

4

Add versioning to the S3 bucket

Inside the aws_s3_bucket resource named app_bucket, add a versioning block with enabled set to true.

Terraform

resource "aws_instance" "web_server" {
  ami           = "ami-12345678"
  instance_type = "t2.micro"

  tags = {
    Name = "WebServerInstance"
  }
}

resource "aws_s3_bucket" "app_bucket" {
  bucket = "my-app-bucket"
  # Your code here to add versioning block
}

Hint

Use a versioning block inside the aws_s3_bucket resource with enabled = true.

Practice

1. What does the resource block in Terraform define?

easy

A. A provider configuration

B. A variable to store user input

C. A cloud service to create and manage

D. A function to run code

Solution

1. Step 1: Understand Terraform resource block purpose

   The resource block tells Terraform what cloud service to create and manage.

2. Step 2: Differentiate from other blocks

   Variables store input, functions run code, and providers configure cloud access, but resources define actual services.

3. Final Answer:

   A cloud service to create and manage -> Option C

4. Quick Check:

   Resource block = cloud service definition [OK]

Hint: Resource blocks create services, not variables or functions [OK]

Common Mistakes:

• Confusing resource with variable or provider blocks
• Thinking resource defines code logic
• Mixing resource with output blocks

2. Which of the following is the correct syntax to declare an AWS S3 bucket resource named my_bucket in Terraform?

easy

A. resource aws_s3_bucket "my_bucket" {}

B. resource aws_s3_bucket my_bucket {}

C. resource "aws_s3_bucket" my_bucket {}

D. resource "aws_s3_bucket" "my_bucket" {}

Solution

1. Step 1: Recall Terraform resource syntax

   Terraform resource syntax requires resource type and name as strings inside quotes: resource "type" "name" {}

2. Step 2: Match correct option

   Only resource "aws_s3_bucket" "my_bucket" {} uses quotes correctly around both type and name.

3. Final Answer:

   resource "aws_s3_bucket" "my_bucket" {} -> Option D

4. Quick Check:

   Resource type and name must be quoted [OK]

Hint: Always quote resource type and name in Terraform [OK]

Common Mistakes:

• Omitting quotes around type or name
• Using quotes inconsistently
• Swapping order of type and name

3. Given this Terraform code snippet:

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

What is the resource type and name?

medium

A. Type: aws_instance, Name: web

B. Type: web, Name: aws_instance

C. Type: ami-123456, Name: t2.micro

D. Type: aws_instance, Name: ami-123456

Solution

1. Step 1: Identify resource type and name in block

   The first quoted string after resource is the type: "aws_instance". The second is the name: "web".

2. Step 2: Confirm values are correct

   AMI and instance_type are attributes, not resource type or name.

3. Final Answer:

   Type: aws_instance, Name: web -> Option A

4. Quick Check:

   Resource type and name = aws_instance, web [OK]

Hint: First quoted string = type, second = name [OK]

Common Mistakes:

• Confusing attributes with resource type or name
• Swapping type and name
• Using attribute values as names

4. What is wrong with this Terraform resource declaration?

resource "aws_s3_bucket" my_bucket {
  bucket = "my-bucket-name"
}

medium

A. Resource name is not quoted

B. Resource type is missing

C. Bucket attribute is invalid

D. Missing provider block

Solution

1. Step 1: Check resource declaration syntax

   Terraform requires both resource type and name to be quoted strings.

2. Step 2: Identify the error

   The resource name my_bucket is not quoted, causing a syntax error.

3. Final Answer:

   Resource name is not quoted -> Option A

4. Quick Check:

   Resource names must be quoted strings [OK]

Hint: Always quote resource names to avoid syntax errors [OK]

Common Mistakes:

• Forgetting quotes around resource names
• Assuming attributes cause errors
• Thinking provider block is mandatory here

5. You want to create two AWS EC2 instances with different names but the same type in Terraform. Which is the best way to name the resources?

hard

A. resource "aws_instance" "aws_instance" {} and resource "aws_instance" "aws_instance" {}

B. resource "aws_instance" "app1" {} and resource "aws_instance" "app2" {}

C. resource "aws_instance" "1" {} and resource "aws_instance" "2" {}

D. resource "aws_instance" "instance" {} and resource "aws_instance" "instance" {}

Solution

1. Step 1: Understand resource naming rules

   Resource names must be unique within the same type to avoid conflicts.

2. Step 2: Evaluate naming options

   resource "aws_instance" "app1" {} and resource "aws_instance" "app2" {} uses unique, descriptive names app1 and app2. Choices that reuse the same name cause errors. The choice using numeric names is valid but less descriptive.

3. Final Answer:

   resource "aws_instance" "app1" {} and resource "aws_instance" "app2" {} -> Option B

4. Quick Check:

   Unique descriptive names prevent conflicts [OK]

Hint: Use unique, clear names for each resource [OK]

Common Mistakes:

• Using duplicate resource names
• Using unclear or numeric-only names
• Ignoring naming uniqueness rules