How palakbhawsar98/terraform-notes works
Project type and purpose
• This is a hands-on Terraform tutorial repo (Infrastructure-as-Code) that demonstrates how to provision AWS resources (EC2 instances, VPCs, remote state).
• It is not a web application but a collection of Terraform modules/examples, each in its own folder, illustrating specific IaC use cases.
File structure
• Top-level demo scripts:
• terraform-ec2-hands-on – EC2 provisioning example
• terraform-vpc-hands-on – VPC + subnets + outputs
• terraform-remote-state-hands-on – remote state configuration
• Each folder contains .tf files:
• providers.tf, main.tf, variables.tf, outputs.tf, etc.
• No source code; all HCL configuration. No tests or CI/CD configs present.
README for additional insights
• Explains Terraform workflow (init, plan, apply)
• Describes providers, state, variables, lifecycle, outputs
• Mentions AWS provider, S3 backend options, typical resource blocks
a. Main components
• Developer workstation running Terraform CLI
• Terraform configuration files (.tf)
• Terraform State (local or remote backend e.g. S3)
• AWS Provider API
• AWS resources:
– VPC
– Subnets (multiple AZs)
– EC2 Instances
b. Relationships & data flow
1. Developer edits .tf files
2. terraform init loads provider plugin
3. terraform plan generates execution plan
4. terraform apply → CLI calls AWS Provider API
5. AWS API provisions VPC, subnets, EC2
6. Terraform writes state to backend (local file or S3)
7. Outputs are returned to CLI
c. Architectural patterns & design principles
• IaC pattern: declarative config → desired state
• State management: remote backend for collaboration/locking
• Module separation: each tutorial folder acts as its own isolated “module”
• Provider abstraction: Terraform plugin architecture
d. Key technologies
• Terraform Core (HCL)
• AWS Provider plugin
• Remote state backend (e.g. AWS S3)
• AWS VPC, EC2 APIs
Elements
• Labels:
• Terraform CLI
• Configuration Directory (with sub-folders)
• Remote State Backend (S3)
• AWS Provider
• AWS Resources (VPC, Subnet(s), EC2 Instances)
• From CLI to AWS Provider API (calls)
• From CLI to State Backend (read/write)
• Between resources (VPC → Subnets → EC2)
• Rectangles for components you control (CLI, config files)