Clicking through a cloud console works for a first experiment, but it leaves no record of what was built and no reliable way to build it again. Infrastructure as Code fixes this by describing servers, networks, and cloud resources in files, so an environment can be created, reviewed, and rebuilt the same way every time.
You'll start with the core idea and why teams adopt it, then look at Terraform, which declares the cloud resources you want and works out the changes needed to reach them. Next comes Ansible, which configures the machines themselves by installing packages, editing files, and managing services from a simple playbook. Because all of it is plain text, the Git habits from the last module apply directly: every infrastructure change can be reviewed and rolled back.
Once your environments are defined in code, you'll be ready for the next module, Containers & Orchestration, where applications are packaged and run on that infrastructure.
The essentials of Infrastructure as Code: how describing infrastructure in files replaces manual setup, and how it improves speed, consistency, and repeatability.
An overview of Terraform, a tool that provisions resources on cloud providers such as AWS, Google Cloud, and Azure from declarative configuration files.
A look at Ansible, an automation tool that configures servers and runs tasks across many machines from simple playbooks.