Source: Dev.to | Dec 19, 2025 (UTC)
(IAM User module reused + output consumed)
This project answers:
1️⃣ Project Structure (CERTIFICATION STYLE)
project-1-iam-reuse/ ├── main.tf └── modules/ └── iam-user/ ├── main.tf ├── variables.tf └── outputs.tf
Enter fullscreen mode
Exit fullscreen mode
variable "user_name" { type = string }
Enter fullscreen mode
Exit fullscreen mode
resource "aws_iam_user" "this" { name = var.user_name }
Enter fullscreen mode
Exit fullscreen mode
output "user_arn" { value = aws_iam_user.this.arn }
Enter fullscreen mode
Exit fullscreen mode
3️⃣ Root Module — Reusing SAME Module Twice
provider "aws" { region = "us-west-1" } module "dev_user" { source = "./modules/iam-user" user_name = "dev-user" } module "prod_user" { source = "./modules/iam-user" user_name = "prod-user" } output "dev_user_arn" { value = module.dev_user.user_arn } output "prod_user_arn" { value = module.prod_user.user_arn }
Enter fullscreen mode
Exit fullscreen mode
terraform init terraform plan terraform apply
Enter fullscreen mode
Exit fullscreen mode
5️⃣ What This Project Demonstrates (EXAM MAPPING)
Exam Topic
Demonstrated
Root module
main.tf
Child module
modules/iam-user
Module reuse
Same module twice
Input variables
user_name
Outputs
user_arn
Output consumption
module.dev_user.user_arn
State behavior
Both users in same state
6️⃣ Answers to Exam Questions (FROM THIS PROJECT)
Q: Can same module be reused multiple times?
✔️ YES — demonstrated by dev_user and prod_user
Q: Where are module outputs stored?
✔️ Terraform state
Q: Does deleting root module delete child resources?
✔️ YES — all resources tracked in state
PROJECT 2 — Module + for_each + Environment Pattern
(S3 module used for dev/prod with for_each)
This project answers:
project-2-s3-env/ ├── main.tf └── modules/ └── s3-bucket/ ├── main.tf ├── variables.tf └── outputs.tf
Enter fullscreen mode
Exit fullscreen mode
modules/s3-bucket/variables.tf
variable "bucket_name" { type = string }
Enter fullscreen mode
Exit fullscreen mode
resource "aws_s3_bucket" "this" { bucket = var.bucket_name }
Enter fullscreen mode
Exit fullscreen mode
output "bucket_name" { value = aws_s3_bucket.this.bucket }
Enter fullscreen mode
Exit fullscreen mode
3️⃣ Root Module — for_each Over Environments
provider "aws" { region = "us-west-1" } locals { environments = { dev = "dev-app-bucket-aj" prod = "prod-app-bucket-aj" } } module "s3" { source = "./modules/s3-bucket" for_each = local.environments bucket_name = each.value } output "bucket_names" { value = { for env, mod in module.s3 : env => mod.bucket_name } }
Enter fullscreen mode
Exit fullscreen mode
terraform init terraform plan terraform apply
Enter fullscreen mode
Exit fullscreen mode
5️⃣ What This Project Demonstrates (EXAM MAPPING)
Exam Topic
Demonstrated
Module + for_each
YES
Environment pattern
dev / prod
locals usage
YES
Output map
YES
Deterministic resource creation
YES
6️⃣ Answers to Exam Questions (FROM THIS PROJECT)
Q: When should for_each be used instead of count?
✔️ When using named keys (dev/prod)
Q: Can modules be used with for_each?
✔️ YES — fully supported
Q: What does module.s3["dev"] represent?
✔️ Dev environment module instance
FINAL CERTIFICATION SUMMARY (MEMORIZE THIS)
Terraform modules encapsulate reusable infrastructure logic.
Root modules compose child modules, pass inputs, and consume outputs.
Modules can be reused, versioned, and instantiated using count or for_each.
All module resources are tracked in a single Terraform state.
For further actions, you may consider blocking this person and/or reporting abuse
Залишити відповідь