devops-infrastructurelisted

# DevOps Infrastructure ## Overview Manual infrastructure changes are incidents waiting to happen. Unversioned configs are undocumented debt. **Core principle:** EVERY piece of infrastructure is defined in code, stored in version control, and deployed through automation. **Violating the letter of this process is violating the spirit of infrastructure engineering.** ## The Iron Law ``` NO MANUAL INFRASTRUCTURE CHANGES - EVERYTHING IS CODE, VERSIONED, AND REVIEWABLE ``` If you clicked through a console UI to create it, it doesn't exist yet. Write the code. ## When to Use Use for ANY infrastructure work: - Provisioning cloud resources - Building container images - Configuring CI/CD pipelines - Setting up deployment strategies - Managing secrets and credentials - Configuring monitoring and alerting - Setting up networking and DNS **Use this ESPECIALLY when:** - Under deadline pressure ("just create it in the console for now") - A quick manual fix seems faster - Someone says "we'll codify it later" - You're setting up a "temporary" environment - Debugging a production issue by hand **Don't skip when:** - It's "just one resource" (one resource becomes twenty) - It's a dev environment (dev environments become templates) - It's a one-time setup (nothing is one-time) ## The Five Phases You MUST complete each phase before proceeding to the next. ### Phase 1: Define Infrastructure as Code **BEFORE creating ANY resource:** 1. **Choose Your IaC Tool** - Terraform: Multi