terraform

Best Practices

• Pin provider versions using pessimistic constraint (~>) to prevent breaking changes
• Use variables for all environment-specific values
• Tag all resources with standard metadata (project, environment, managed-by)
• Use remote state backend for team collaboration
• Organize resources logically with clear naming conventions
• Define outputs for values needed by other configurations
• Use data sources instead of hardcoding resource references
• Variable and resource names must use snake_case
• No hardcoded credentials (AWS keys, passwords, tokens)
• Maximum 50 resources per generation
• Separate concerns into standard files (main.tf, variables.tf, outputs.tf, providers.tf, terraform.tf)

Documentation Sources