[DevOps] Terraform - How to manage multi-environments

Connect AWS, GitHub, and Jenkins to set up the lab environment; create a user, grant EC2 and S3 full access, generate an SSH key, configure the terminal, and add credentials.

Explore how to organize Terraform for multiple environments by using separate folders and distinct state files for dev, staging, and production, driven by environment variables.

Learn to run terraform via Jenkins by using GitHub branches for dev, staging, and prod, with backend state in env-specific S3 buckets and a multi-branch pipeline.

Explore how Terraform workspaces manage multiple state files and isolate resources across dev, staging, and production using a single configuration, with S3 backend and environment-specific vars.

Leverage Terraform workspaces via Jenkins to manage multi-environment deployments with separate tfvars per environment and independent state files, enabling environment-specific plans, applies, and automatic workspace-based subfolders.

Organize terraform with per-environment subfolders that hold backend configurations and environment-specific variables while sharing a configuration. Initialize, plan, and apply across dev, staging, and production using S3 backends and tfvars.

Implement a Jenkins-driven Terraform workflow using per-environment subfolders for dev, staging, and production backends and variables, including state files and init, plan, and apply.

Compare three solutions for managing different environments and the Terraform state file, and explain how project needs and environment requirements shape the best approach.