Why Infrastructure as Code Is Revolutionizing Cloud Operations with Ansible & Terraform

The talk, delivered by Wang Xin from Alibaba Cloud Open Platform, introduces the concept of Infrastructure as Code (IaC) and its importance in the cloud era.

The presentation is divided into four parts: why IaC emerged, an introduction to open‑source tools Ansible and Terraform, case studies of IaC, and common issues with best practices.

1. Understanding Infrastructure as Code in the Cloud Era

With rapid traffic growth, console‑only management is insufficient; exposing capabilities via native APIs enables developers and partners to integrate cloud services programmatically.

IaC addresses challenges such as security, performance, stability, compliance, and maintainability by providing a declarative configuration that ensures consistent environments for applications.

Key characteristics of IaC include self‑documenting configuration files (often YAML or JSON), version control, and the ability to protect and iterate infrastructure safely.

2. Ansible and Terraform

Terraform is an open‑source, multi‑cloud orchestration tool that defines infrastructure resources. It works with providers (e.g., Alibaba Cloud, AWS, OpenStack) and provisioners to manage resources declaratively.

Ansible is a widely adopted configuration‑management tool that operates agent‑less and uses a declarative YAML playbook format. Its architecture includes an inventory for host definitions, modules for tasks, and plugins for extensions.

Inventory : defines host groups and connection details.

Playbook : a YAML file describing desired state and tasks.

Modules : reusable units that perform actions on remote hosts.

Terraform maintains a state file (local or remote) to track the actual versus desired infrastructure, supports a plan command for previewing changes, and can execute tasks concurrently based on dependency analysis.

3. Case Study of Infrastructure as Code

Creating an ECS instance on Alibaba Cloud requires a VPC, switch, and storage, each with dependencies. Using Terraform, developers simply declare these resources; the engine resolves dependencies, generates an execution plan, and creates resources in the correct order, eliminating manual scripting.

The case demonstrates how IaC reduces complexity, ensures consistency, and accelerates provisioning compared to imperative scripts.

4. Common Issues and Best Practices

Best practices include giving clear names to plays and tasks, using check‑mode to validate changes, separating variables into -var-file files, and isolating environments with distinct variable sets.

For Terraform, regularly run terraform fmt to format code, use terraform plan for preview, and store state remotely (e.g., OSS or S3) for team collaboration.

Overall, IaC enables rapid, reliable, and cost‑effective infrastructure management, supporting continuous delivery pipelines and improving operational efficiency.