Infrastructure as Code
Terraform Modules Teams Actually Adopt
Design modules with clear contracts, state boundaries, and reviewable plans for multi-team repositories.
- Duration
- 5 weeks
- Format
- Self-paced with mentor checkpoints
- Skill focus
- Intermediate
- Project intensity
- Medium
360,000 KRW
Informational tuition reference — no checkout on this static site.
Program narrative
We walk from flat directories to versioned modules, remote state hygiene, and policy checks that catch drift before merge. You will pair on a fictional multi-account topology grounded in patterns common in Korean enterprise markets.
Included focus areas
- • Remote state layout with least-privilege roles
- • Module versioning and consumer upgrade paths
- • Plan policies that fail noisy changes early
- • Workspace versus stack tradeoffs spelled out
- • Import workflows for brownfield resources
- • Documentation blocks generated from module metadata
- • Hand-off notes for security reviewers
Outcomes you can show
- Publish a module consumed by two fictional teams
- Ship a policy bundle that blocks three risky patterns
- Record a five-minute walkthrough for internal enablement
Mentor of record
Yuna Kim
Infrastructure-as-code specialist who prefers readable plans over clever hacks.
Participant notes
Policy-as-code week saved us from another surprise NAT change. Docs templates are now our default.
Checkpoint reviews were specific about naming and state keys. Took longer than expected but worth it.
Straight answers
Examples lean on a major cloud provider; patterns port to others with mentor guidance.