Infrastructure as Code
Ansible automates configuration and provisioning over SSH.
On this page
Use this page for fast recall. Use Full documentation when you want the complete end-to-end path.
A simple 5-step flow you can follow when using Ansible in real work.
1) Setup
Install/run the tool and confirm version. Create a minimal config.
2) Small change
Do one small action end-to-end to prove the workflow.
3) Validate
Check output, logs, and status. Catch mistakes early.
4) Automate
Convert it into a repeatable script or pipeline step.
5) Productionize
Add safety: secrets, rollback, observability, and docs.
These are practical sequences you can copy into your own checklist or runbook.
Goal: Make server provisioning repeatable and safe to run multiple times.
- Define an inventory and host groups.
- Start with one play that installs packages and configures a service.
- Run with `--check --diff` first, then real run.
- Refactor into roles and tag your tasks.
- Add CI linting and run against staging before prod.
- Inventory
- Playbooks
- Roles
Learning path (high-level):
- Inventory design
- Playbook authoring
- Role-based reuse
Ping hosts
Command
ansible all -m pingRun playbook
Command
ansible-playbook site.ymlCheck syntax
Command
ansible-playbook --syntax-check site.ymlShort descriptions and practical intent. Search, filter, copy, and reuse.
Showing 16
ansible --versionShow Ansible version.
ansible all -m pingConnectivity check via ping module.
ansible all -a 'uptime'Run ad-hoc command on all hosts.
ansible web -a 'df -h'Run command on group `web`.
ansible-inventory -i inventory.ini --listPrint parsed inventory.
ansible-inventory -i inventory.ini --graphShow inventory graph.
ansible-playbook site.ymlRun a playbook.
ansible-playbook site.yml --checkDry run playbook changes.
ansible-playbook site.yml --diffShow diffs for changed templates/files.
ansible-playbook site.yml --limit webRun playbook on a group.
ansible-playbook site.yml -t nginxRun only specific tags.
ansible-playbook site.yml --start-at-task "Install packages"Resume from a task.
ansible-doc copyShow module docs.
ansible-galaxy collection listList installed collections.
ansible-galaxy collection install community.generalInstall a collection.
ansible-galaxy init role_nameCreate a new role structure.
Small blocks you can drop into your terminal, config, or runbook.
Run a playbook safely first
bash
ansible-playbook -i inventory.ini site.yml --check --diff
ansible-playbook -i inventory.ini site.ymlWhen things break, follow this order to stay calm and move fast.
- If SSH fails: confirm host, key, user, and `ansible_ssh_common_args` settings.
- If tasks are not idempotent: use proper modules instead of raw shell commands.
- If variables behave oddly: print `-vvv` and confirm inventory precedence.
The common mistakes that slow people down when using Ansible.
- Copy-pasting commands without understanding inputs/outputs and side effects.
- Not documenting defaults (ports, paths, credentials) and then getting stuck in prod.
- Skipping logs and metrics when troubleshooting; always collect evidence first.
Do these tasks in order. You will feel the tool instead of just reading about it.
- Install or run the tool locally (or in Docker) and verify it works with a hello-world action.
- Create a minimal config and run the most common command 3 times (with a small change each time).
- Break something on purpose and document how you debugged it in your Notes.
Use these to test if you truly understand the basics (and can explain them clearly).
- Explain the tool’s role in a real CI/CD pipeline from commit to production.
- Describe the most common failure you’ve seen with this tool and how you fixed it.
- What would you monitor/alert on for this tool in production?