How valentyna6/final-work-bootcamp works
Project type and purpose
• From the file tree and README, this is a Terraform-based Infrastructure-as-Code project targeting AWS.
• It defines reusable Terraform modules for key infrastructure components: an application load balancer (alb), auto-scaling WordPress servers (asg), RDS, ECR, and self-hosted GitHub runners.
File structure
• Top level:
• terraform/ (root folder for Terraform configuration)
• terraform.tfstate (state file)
• README.md
• Inside terraform/:
• main.tf, providers.tf, variables.tf, outputs.tf – orchestrate the modules and define provider settings
• modules/
– alb/
– asg/
– rds/
– ecr/
– github-runner/
– security/
• Each module has main.tf, variables.tf, outputs.tf (plus user_data scripts for asg and github-runner).
README for additional insights
• The README is minimal (“Final-Work-Bootcamp, test collaborator access”).
Diagramming conventions and elements
• Clear labels for each module and AWS resource
– Orange for compute (EC2/ASG/GitHub runners)
– Green for data services (RDS, ECR)
– Purple for networking (VPC, subnets, SG)
• Resources by VPC subnet (public vs. private)
Detailed breakdown of components
• security (SG definitions)
• alb → AWS::ApplicationLoadBalancer
• asg → AWS::AutoScalingGroup with user_data_wp.sh
• rds → AWS::RDS::DBInstance
• ecr → AWS::ECR::Repository
• github-runner → AWS::EC2::Instance autoscaled via ASG or Launch Template with user_data_github_runner.sh
• AWS Environment Boundary
• Internet Gateway → ALB → ASG(WordPress)
• ASG(WordPress) ↔ RDS in private subnet
• GitHub Runner ASG in private subnet, outbound to GitHub SaaS & ECR
• Annotations for Security Group attachments