Terraform / OpenTofu — Infrastructure as Code
A hands-on Terraform and OpenTofu workshop from fundamentals to CI/CD: state management, building modules, multi-cloud, and license migration to OpenTofu — not an IaC tool comparison, a practical rollout.
IaC as a team practice, not just HCL syntax
Writing your first .tf file is the easy part — the harder part is safely managing infrastructure state across a team of multiple engineers, without the risk of overwriting someone else’s changes or losing sync with real infrastructure. From day one, the workshop treats Terraform/OpenTofu as a team practice, not an individual tool.
Modules and multi-cloud as the foundation for scaling
Repeating the same configuration for every new environment is a fast track to inconsistency and mistakes. Participants learn to build their own reusable modules and to manage a multi-cloud environment with one consistent repository structure, matching the dev/staging/prod pattern.
Migrating to OpenTofu without the theory lecture
HashiCorp’s license change from open source to BUSL has led many teams to consider or already carry out a migration to the OpenTofu fork. Instead of describing the licensing differences in theory, the workshop shows a practical migration process for existing Terraform code — step by step, on a real example, ready to repeat in your own environment.
Benefits
- Write Terraform/OpenTofu configuration from scratch for a real cloud environment
- Manage state safely as a team, including remote state and state locking
- Build reusable modules for repeatable infrastructure patterns
- Integrate Terraform/OpenTofu with a CI/CD pipeline and plan a migration to OpenTofu
Who is this training for?
Prerequisites
- Basic knowledge of at least one cloud provider (AWS, Azure, or GCP)
- Command-line familiarity and basic Git knowledge
Training program
Infrastructure as Code fundamentals with Terraform/OpenTofu
- Declarative infrastructure management — philosophy and core commands (plan, apply, destroy)
- HCL syntax, resources, variables, and outputs
- Providers and managing multiple cloud resources in one configuration
- The origin of the OpenTofu fork and licensing differences from Terraform (BUSL vs MPL)
State management and team workflows
- The state file — what it is and why it requires careful management
- Remote state (S3, Azure Storage, Terraform Cloud) and team state locking
- Importing existing infrastructure into Terraform/OpenTofu management
- Handling and detecting configuration drift
Modules and reusable patterns
- Building your own Terraform/OpenTofu modules for repeatable patterns
- Repository structure for multi-environment setups (dev/staging/prod)
- Managing dependencies between modules and workspaces
- Using public and internal module registries
CI/CD, multi-cloud, and migrating to OpenTofu
- Integrating Terraform/OpenTofu into a CI/CD pipeline (plan on PR, apply on merge)
- Managing a multi-cloud environment with one consistent configuration
- A practical migration of existing Terraform code to OpenTofu
- Testing infrastructure (Terratest, policy validation) before rollout
Delivery Methods
Online
- Convenience of participating from anywhere
- Interactive live sessions with trainer
- Materials available for 30 days
- No travel costs
On-site
- Direct contact with trainer and group
- Intensive hands-on workshops
- Networking with other participants
- Full focus on learning
Frequently asked questions
How is this different from Advanced IaC — Terraform vs Pulumi vs AWS CDK in our catalog?
That course compares different IaC tools, helping you choose the right one for a given project. This training is a practical hands-on workshop with a single stack — Terraform and its fork OpenTofu — from HCL syntax fundamentals, through state management and modules, to CI/CD integration and license migration, without comparing to other tools.
Should I learn Terraform or go straight to OpenTofu?
The syntax and mechanics of both tools are nearly identical — OpenTofu is a fork of Terraform created after HashiCorp changed its license from open source (MPL) to BUSL. In the training we teach one skill set that works in both tools, and we show a practical process for migrating existing Terraform code to OpenTofu.
How do I safely manage the state file across a team of multiple engineers?
The key is moving the state file from a local disk to a remote backend (e.g. S3 with DynamoDB for locking, or Terraform Cloud) with a locking mechanism that prevents two engineers from making concurrent changes. In the workshop we configure remote state and show typical conflict scenarios and how to resolve them.
Is three days enough to independently manage production infrastructure in Terraform?
Three days is enough to build a solid foundation: writing configuration, managing state safely, building modules, and integrating with CI/CD on a practical multi-cloud environment. Participants leave with a ready repository template and a rollout checklist to apply in their own organization.
Request a quote
Funding Options
Check funding options for your company
Development Services Database
An instrument for micro, small and medium-sized companies — check whether it applies to your organisation
Check availabilityNational Training Fund
An instrument for employers — we help you check whether it can be applied
Learn moreTrusted by
We train teams at Poland's largest companies
Interested in this training?
Contact us - we'll prepare an offer tailored to your organization's needs.