How amanpathak-devops/terraform-for-aws works
Project Type and Purpose
• This is an Infrastructure-as-Code (IaC) repository using Terraform to provision AWS services.
• It demonstrates two styles:
• Non-Modularized: individual Terraform projects, each directly defining AWS resources (e.g., ALB-EC2, API-Gateway-POST, Three-Tier-Application, etc.).
• Modularized: a reusable set of Terraform modules (VPC, EC2, Lambda, S3, SNS) plus environment-specific root configurations that assemble those modules.
Main Components
a. Code Repository
– Folders: Non-Modularized/, Modularized/ (with Terraform-Modularized/ root), CI configs (.circleci/, .github/workflows/, Jenkinsfile)
b. CI/CD Pipelines
– CircleCI or GitHub Actions pipeline (terraform.yml)
– Jenkins pipeline (Jenkinsfile)
c. Terraform CLI & Backend
– terraform init/plan/apply in each project
– backend configuration files (backend.tf) pointing at remote state (S3 or Terraform Cloud)
d. AWS Provider & Account
– Single AWS account (or one per environment)
– Authentication via AWS credentials or role assumption
e. AWS Resources
– Core modules: VPC (subnets, route tables), EC2, Lambda, S3, SNS
– Additional services: RDS, DynamoDB, CloudFront, API Gateway, ASG/ELB, CloudWatch, IAM, etc.
Relationships and Interactions
• The CI/CD system monitors GitHub for changes → triggers Terraform workflow → invokes Terraform CLI on a root folder (either a non-modular project or a modular root).
• Terraform CLI calls out to AWS via the AWS provider.
• For the Modularized path: root configurations (e.g., EC2-Instance, S3-Bucket) depend on child modules in Modules/ (Terraform-VPC → Terraform-EC2 → Terraform-Lambda, etc.).
• The modules encapsulate resource definitions and expose input/output variables; root modules wire input variables (e.g., VPC ID) into child modules.
• Terraform uses a remote state backend (S3) to store state files and to share outputs between modules/environments.
Architectural Patterns & Design Principles
• Infrastructure as Code: all resources are declared in source-controlled Terraform files.
• Modularization: reusable modules for common services to reduce duplication and simplify maintenance.
• Environment Isolation: dev.tfvars (and other .tfvars per environment) drive configuration differences.
• CI/CD Integration: pipelines automate validation, planning, and apply stages.
• Separation of Concerns:
• Non-Modularized examples illustrate direct provisioning – ideal for learning or small demos.
• Modularized approach abstracts common patterns into modules for production-scale use.
Essential Elements
• Code push → CI/CD → Terraform init/plan/apply
• Terraform CLI → Remote State Backend
• Terraform CLI → AWS Provider → AWS Resources
• Root module → Child module dependencies
• Code (blue), CI (purple), State (gray), Modules (teal), AWS services (orange).