Contract

• Input: infrastructure requirements (compute, storage, network, identity, policies).
• Output: IAC module definitions + state rules + policy checklist.
• Side effects: may create resources when executed (plan/apply).
• Dependencies: cloud provider access (AWS / GCP / Azure / local).
• Stop condition: definitions and rules saved.
• Risk: medium — IAC errors cause outages or data loss; requires testing (terraform plan / dry-run).
• Boundary: defines infrastructure; execution requires explicit approval and testing.

Infrastructure as Code Design

Design reproducible infrastructure — compute, network, storage, identity — with version control, state management, and policy enforcement.

Process