terraform-infrastructure_skill

Overview

This skill provides a comprehensive Terraform infrastructure-as-code workflow for provisioning and managing cloud resources across AWS, Azure, GCP, Kubernetes, and multi-cloud environments. It covers providers, resources, modules, state management, workspaces, and enterprise patterns to build reproducible, version-controlled infrastructure. The skill is focused on practical patterns for teams: reusable modules, secure provider auth, state backends, and multi-environment deployments.

How this skill works

The skill inspects and explains Terraform core concepts and HCL patterns, including provider configuration, resource declaration, data sources, locals, functions, and meta-arguments. It walks through a typical Terraform workflow (init → plan → apply → destroy) and shows how to compose modules, manage remote state, use workspaces, and implement lifecycle and provider aliasing for multi-region or multi-account setups. It also highlights validation, conditional logic, dynamic blocks, and enterprise best practices like remote state locking and CI/CD integration.

When to use it

• Provision cloud infrastructure across AWS, Azure, GCP, or mixed-cloud environments
• Build reusable modules for team or organizational standards
• Manage environment-specific state (dev, staging, prod) with remote backends
• Migrate manual infrastructure to version-controlled IaC
• Orchestrate multi-tier applications, Kubernetes clusters, databases, and networks
• Implement disaster recovery, multi-region deployments, and GitOps workflows

Best practices

• Store state in a remote backend with locking (S3 + DynamoDB, GCS, or Terraform Cloud) to avoid conflicts
• Use modules to encapsulate repeatable patterns and expose minimal, validated inputs
• Keep secrets out of code; inject credentials via environment variables, Vault, or CI secrets
• Use terraform plan in CI to require review before terraform apply in production
• Pin provider versions and use aliases for multi-account or multi-region resources

Example use cases

• Create a reusable VPC + subnet module consumed by multiple application teams
• Deploy a Kubernetes cluster on AWS with managed database and load balancer using modules
• Migrate on-prem resources to cloud by modeling resources with data sources and apply
• Implement blue/green or canary infrastructure updates with workspaces and lifecycle rules
• Standardize tagging, monitoring, and IAM across accounts with centralized modules