1.3 : First Resource — Provision an S3 Bucket with Terraform

⏱️ Prerequisite: Day 1 (IaC Concepts) + Day 2 (Providers & init) ✅

📁 Repo: github.com/Push/terraform-aws-labs → /day03/

🎯 Goal: Go from .tf file → live AWS S3 bucket → update tags → destroy — all with Terraform commands.

🧠 Why Start with S3?

✅ Simplest AWS resource (no dependencies like VPC/subnets)
✅ Instant creation (~1 sec)
✅ Global namespace → teaches uniqueness constraints
✅ Perfect for learning the Terraform workflow loop:

init → plan → apply → modify → plan → apply → destroy

📄 Step-by-Step: `main.tf` for S3 Bucket

✏️ `day03/main.tf`

terraform {
  required_version = ">= 1.5.0"
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 6.7.0"
    }
  }
}

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

# 🪣 S3 Bucket Resource
resource "aws_s3_bucket" "first_bucket" {  # ← Logical name (for Terraform internals)
  bucket = "tech-tutorials-push-2025"        # ← Must be GLOBALLY unique!
  tags = {
    Name        = "my-bucket"
    Environment = "dev"
  }
}

🔍 Key Notes:

Field	Why It Matters
`bucket`	Must be globally unique across all AWS accounts/regions — use your name + year
`tags`	Optional, but best practice for cost allocation & filtering
`first_bucket`	Internal reference (e.g., `aws_s3_bucket.first_bucket.id`) — name it meaningfully!

💡 Pro Tip: Use random provider for unique names in real projects — coming soon!

🧠 Why Start with S3?

📄 Step-by-Step: main.tf for S3 Bucket

✏️ day03/main.tf

🔍 Key Notes:

🧪 Lab: Full Terraform Lifecycle

📄 Step-by-Step: `main.tf` for S3 Bucket

✏️ `day03/main.tf`