I will write production terraform modules for aws eks with argocd gitops

I've been writing Terraform since 0.11. The difference between "it works on my machine" and "it works in production for 3 years" is modules, state management, and GitOps.

What you get:

 Production-grade modules VPC (public/private/subnet), EKS (managed node groups, IRSA, encryption), RDS (encrypted, backup, read replica), S3 (versioned, lifecycle, replication), IAM (least privilege, OIDC)

 Terraform Cloud/Enterprise Workspaces per env, run triggers, policy checks (Sentinel/OPA), private registry, drift detection

 GitOps with ArgoCD App-of-Apps pattern, auto-sync + prune + self-heal, Kustomize/Helm, declarative secrets (SealedSecrets/External Secrets + Vault)

 CI/CD for Terraform GitHub Actions: fmt validate plan policy check apply (manual approval on prod)

 Policy as Code OPA/Kyverno: required tags, no public SG, encrypted volumes, approved AMIs only

 Disaster Recovery Velero backups to S3 (cross-region), scheduled + on-demand, tested restore runbook

 FinOps Infracost on every PR, Kubecost in cluster, tagging enforcement, rightsizing recommendations

 Documentation Auto-generated (terraform-docs), architecture diagrams, runbooks, onboarding guide

Stack: Terraform, Terragrunt, AWS..