Resource types and names in Terraform - Commands & Configuration

Introduction

When you create infrastructure with Terraform, you define resources. Each resource has a type and a name. The type tells Terraform what kind of thing to create, like a server or a database. The name is how you refer to that resource in your code.

When you want to create a virtual machine in the cloud.

When you need to set up a storage bucket for your files.

When you want to manage a database instance alongside your app.

When you need to create a network or firewall rule.

When you want to organize your infrastructure code clearly.

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_instance" "my_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "MyServer"
  }
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-unique-bucket-terraform-12345"
  acl    = "private"
}

This file defines two resources using Terraform:

• aws_instance my_server: Creates a virtual machine (server) in AWS with a specific image and type.
• aws_s3_bucket my_bucket: Creates a private storage bucket with a unique name.

The resource keyword is followed by the resource type (like aws_instance) and the resource name (like my_server). The name is how you refer to this resource inside Terraform.

Commands

This command sets up Terraform in the current folder. It downloads the AWS provider plugin so Terraform can talk to AWS.

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 required for your infrastructure.

This command shows what Terraform will do if you apply the configuration. It previews the resources it will create.

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_instance.my_server will be created

  + resource "aws_instance" "my_server" {

      + ami                          = "ami-0c55b159cbfafe1f0"

      + instance_type                = "t2.micro"

      + tags                        = {

          + "Name" = "MyServer"

        }

    }



  # aws_s3_bucket.my_bucket will be created

  + resource "aws_s3_bucket" "my_bucket" {

      + acl                          = "private"

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

    }



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

This command creates the resources defined in the configuration. The flag skips the confirmation prompt to make it faster.

Terminal

terraform apply -auto-approve

Expected Output

aws_instance.my_server: Creating...

aws_s3_bucket.my_bucket: Creating...

aws_s3_bucket.my_bucket: Creation complete after 2s [id=my-unique-bucket-terraform-12345]

aws_instance.my_server: Still creating... [10s elapsed]

aws_instance.my_server: Creation complete after 15s [id=i-0abcd1234efgh5678]



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

→

-auto-approve - Skip manual approval prompt

This command lists all resources Terraform is currently managing. It shows the resource types and names.

Terminal

terraform state list

Expected Output

aws_instance.my_server

aws_s3_bucket.my_bucket

Key Concept

If you remember nothing else from this pattern, remember: the resource type tells Terraform what to create, and the resource name is how you refer to it in your code.

Common Mistakes

Using the same resource name for two different resources of the same type.

Terraform requires unique names per resource type to track them correctly. Duplicate names cause errors.

Give each resource a unique name within its type, like aws_instance.my_server and aws_instance.my_server2.

Confusing resource type with resource name and using invalid names.

Resource type must be a valid provider resource, and names must be simple identifiers without spaces or special characters.

Use correct resource types from the provider documentation and simple lowercase names with underscores if needed.

Summary

Define resources in Terraform using resource type and resource name.

Use terraform init to set up providers before creating resources.

Use terraform plan to preview changes and terraform apply to create resources.

Use terraform state list to see all managed resources with their types and names.