Camp Fire Academy
Learning path
Complete UI/UX Masterclass UI/UX Design Foundations UI/UX Design Intermediate Advanced UX Strategy
Specialisations
Fintech & Banking UI/UX UI/UX with AI Training UX for Leaders Design Thinking Figma Training
Most requested
AI for Workplace Productivity Excel for Business Power BI & Business Intelligence Cybersecurity Awareness PDPA Compliance Data Protection Officer Browse the full catalogue →
For teams
Corporate & In-House Training LMS & Self-Paced Learning Events
Company
About Contact Verify Certificate WhatsApp

Infrastructure as Code

Every team that clicks through a cloud console eventually reaches the same point: the staging environment no longer matches production, nobody can say exactly how either was built, and rebuilding one would take a week of archaeology. Infrastructure as code fixes that by making the repository the description of what exists. Two days on doing it properly, including the parts that go wrong: state files, drift, and the destroy that takes down more than intended.

Programme Agenda

Why Declarative, and What It Costs

Describing desired state rather than steps. What you gain in reproducibility and review, and the genuine costs: a new language, a state file to protect, and a slower path for urgent changes.

Providers, Resources and Dependencies

The basic building blocks. Implicit and explicit dependencies, the resource graph, and reading a plan output properly before approving it.

State: The Part That Bites

What the state file holds and why it is sensitive. Remote backends, locking to prevent concurrent applies, and recovering from a corrupted or diverged state. Importing existing resources.

Variables, Outputs and Secrets

Parameterising a configuration without making it unreadable. Where secrets belong, which is not the repository and not the state file if you can avoid it.

Modules and Reuse

Writing a module with a sensible interface, versioning it, and the balance between reuse and the over-abstracted module nobody can debug. Registry modules and when to trust them.

Environment Separation

Workspaces, directory-per-environment and separate state. Keeping development, staging and production genuinely isolated while sharing module code.

Drift, Review and Pipelines

Detecting manual changes made in the console, deciding whether to revert or absorb them, and running plan and apply through a pipeline with a human approval on the plan.

Dangerous Changes

Reading a plan for resource replacement, protecting stateful resources from accidental destruction, and rehearsing the change that would have taken production down.

Learning Outcomes:
Explain the trade-offs of declarative infrastructure honestly
Read a plan output and predict what an apply will actually do
Manage remote state with locking, and recover from state problems
Import existing manually created resources under management
Handle variables and secrets without putting credentials in the repository
Write a reusable module with a clean interface and version it
Separate environments while sharing module code
Detect drift and run plan and apply through a reviewed pipeline

Duration: 2 Days (16 Hours)
Training Hours: 9:00 AM to 5:00 PM
Level: All levels
Training Mode: Physical, Online, or Hybrid
HRD Corp SBL-KHAS Claimable
Certificate of Completion included

Frequently Asked Questions

Cloud and infrastructure engineers, system administrators, DevOps engineers and developers who provision their own infrastructure. Teams migrating away from console-built environments are the typical audience.

The exercises run in Terraform or OpenTofu, whose configuration language is close enough that the material serves both. Concepts such as state, drift and module design apply to other declarative tools as well.

Working familiarity with a cloud platform: what a virtual network, an instance and an identity role are. Participants without that should take Cloud Engineering Foundations first.

Only to draw the boundary. Provisioning infrastructure and configuring what runs on it are different problems, and the session is clear about which tools belong on each side of that line.

Yes, this programme is HRD Corp SBL-KHAS claimable. Our team can assist your HR department with the documentation required for the grant application.

Yes. Any programme can be booked as a team day. Everyone works the same brief together, so your people come away having built something and knowing each other better.

If you are claiming under HRD Corp, the session has to fall at least 14 days after your HRD Corp approval. If you are not claiming, the date is flexible and we work around your calendar.

Put them on the self-paced e-learning instead. Your team works through the modules on our LMS in their own time, sits the assessment, and earns the same certificate, so nobody has to clear a full day together.

More in Cloud, DevOps and Platform Engineering