Terraform

At Zoos Global, all infrastructure resources are defined and managed as code using Terraform.

Repository Layout

Our infrastructure repositories follow a multi-environment layout:

infra-provisioning/
├── modules/
│   ├── ecs-service/
│   ├── database/
│   └── networking/
├── environments/
│   ├── dev/
│   │   ├── main.tf
│   │   ├── variables.tf
│   │   └── outputs.tf
│   ├── staging/
│   └── prod/

State Management

• Terraform state is stored remotely in Amazon S3 buckets with versioning enabled.
• State locking is enforced using DynamoDB tables.
• Never commit .tfstate files to git. Our .gitignore strictly blocks them.

Best Practices

1. Variables and Outputs: Always document variables and outputs using description fields.
2. Resource Tagging: All resource blocks must include standard resource tags:

   tags = {
     Environment = var.environment
     Project     = "zoosglobal"
     ManagedBy   = "terraform"
   }

3. Format and Lint: Format all Terraform code using terraform fmt -recursive before committing.