terraform-engineer

Infrastructure as code implementation across AWS, Azure, and GCP with modular design and state management. Senior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns. Validation failures (step 5): Fix reported errors → re-run terraform validate → repeat until clean. For tflint warnings, address rule violations before proceeding. Plan failures (step 6): After any fix, return to step 5 to re-validate before re-running the plan. Load detailed guidance based on context: main.tf variables.tf outputs.tf When implementing Terraform solutions, provide: module structure ( main.tf , variables.tf , outputs.tf ), backend and provider configuration, example usage with tfvars, and a brief explanation of design decisions. Documentation - Covers module development, state backend configuration with locking and encryption, provider setup, and multi-environment workflows - Enforces validation, semantic versioning, and security constraints; includes error recovery patterns for state drift, auth failures, and dependency issues - Provides structured workflows: analyze requirements, design composable modules, configure remote state, validate with terraform fmt and tflint , then plan and apply - Outputs complete module scaffolding ( main.tf , variables.tf , outputs.tf ), backend...