Week 4 Worklog

Week 4 Objectives

  • Transition from Peering to AWS Transit Gateway (TGW) for scalable networking.
  • Deep dive into EC2 optimization (Auto Scaling, Purchasing Options).
  • Standardize the development workflow with Git/GitHub.

Tasks to be carried out this week

DayTaskStart DateCompletion DateReference Material
2- Advanced Networking: Deployed Transit Gateway.
- Architectural Analysis: TGW (Hub-and-Spoke) vs. Peering (Mesh). Validated TGW’s efficiency in simplifying routing tables for multi-VPC environments.		09/29/202509/30/2025REFER HERE
3- EC2 Optimization:
 + Auto Scaling Group (ASG): Implemented dynamic scaling policies based on CPU utilization.
 + Cost Strategy: Analyzed Spot Instances (90% savings) vs. Reserved/Savings Plans.		10/01/202510/02/2025REFER HERE
4- Source Control Governance:
 + Enforced Git practices: git clone, branching strategies, PR reviews.
 + Resolved merge conflicts in collaborative scenarios.		10/03/202510/04/2025REFER HERE
5- Pre-Proposal: Brainstormed project feasibility, tech stack selection, and module division (BE/FE/DevOps).10/05/202510/06/2025

Week 4 Achievements

  • Mastered the setup and configuration of AWS Transit Gateway, understanding its advantages over VPC Peering (e.g., support for complex multi-VPC and resource connections).
  • Gained a solid understanding of Amazon EC2’s key features:
    • Flexible instance configurations.
    • Cost optimization through various pricing models.
  • Recognized Transit Gateway as the enterprise standard for centralizing network connectivity, eliminating the complexity of managing N*(N-1)/2 peering connections.
  • Defined a compute strategy: Spot Instances for stateless/fault-tolerant workloads, Reserved for steady-state databases.
  • Established a clean Git Flow, readying the team for parallel development.