How velez94/terragrunt_aws_gitops_blueprint works
Project Type and Purpose
• This is an infrastructure-as-code GitOps blueprint. It uses Terragrunt to orchestrate Terraform modules that provision AWS infrastructure (VPC, IAM, SSM, EKS) and then bootstraps an Argo CD–driven GitOps pipeline on the EKS cluster.
• Key goals: modular infra setup, multi-environment support, automated application deployment via Argo CD.
Main Components
a. Git Repositories
• Infra Repo: hosts Terragrunt and Terraform code.
• GitOps App Repos: contain cluster-addons and platform resources.
b. Terragrunt/Terraform Layer
• common/ (variables, providers, environment configs)
• modules/terraform-aws-* (IRSA for EKS, SSM parameter store)
• infrastructure/
• network/vpc
• iam/eks_role
• ssm/parameter_store
• containers/eks_control_plane
• containers/gitops_bridge (Argo CD bootstrap: ApplicationSets).
c. AWS Infrastructure
• VPC: networking, subnets, security groups.
• IAM: EKS control-plane role.
• SSM Parameter Store: central config store.
• EKS Cluster (control plane + worker nodes).
d. GitOps Bridge & Argo CD
• On EKS: Argo CD server & ApplicationSets.
• Argo CD syncs cluster-addons and platform resources from Git.
Relationships & Data Flow
• [Git Infra Repo] → Terragrunt CLI → Terraform → [AWS Infrastructure]
• [AWS Infrastructure] includes VPC → IAM → SSM → EKS Cluster.
• [GitOps Bridge] (via Terragrunt) deploys Argo CD onto EKS.
• [Argo CD] ← polls → [Git App Repos] → applies → EKS cluster workloads.
• Feedback loops: Argo CD continuously reconciles desired state.
Architectural Patterns & Principles
• Infrastructure as Code (Terragrunt + Terraform modules).
• GitOps (declarative desired-state in Git, continuous reconciliation).
• Modular design (common configs + reusable modules).
• Multi-environment layering (Terragrunt environment.hcl).
• Separation of concerns: infra provisioning vs. app deployment.