Terraform 101: Your First Infrastructure as Code
For a long time my idea of "infra provisioning" was logging to the console, making a few clicks through a few pages and done. It worked until it didn't . Until I had to recreate an environment and had
Aayush Darange
Cloud & DevOps from the ground up - AWS, infrastructure, pipelines, and everything in between.
Latest articles
Ansible Part 7 - Collections, Execution Environments and Ansible Navigator
Now that we've come a long way, from, understanding what Ansible is, to writing playbooks, encrypting secrets, building roles. This final one is about what happens when Ansible grows beyond a single p
Ansible Part 6 - Jinja2 Templates and Roles
As your ansible usage matures, you realize that coping static config files is not good enough. You need different ports on staging vs production. Also, a single playbook starts becoming a nightmare, t
Ansible Part 5 - Loops, Handlers and Tags
As we move ahead, playbooks start getting long. You're copying the same task block with different values. You're restarting services manually after config changes. You're running the entire playbook j
Ansible Part 4 - Secrets, Facts and Conditional Tasks
Secrets - passwords, API keys, credentials. You just can't paste them in YAML and push them to your repo. System awareness - your playbook might need to behave differently depending on the host. Condi
Ansible Part 3 - Variables, Because Hardcoding is a TRAP!
Variables are what turn a playbook from a one-trick script into something genuinely reusable. This part covers everything you need to know about them. What is a Variable in Ansible? Same concept as a
Ansible Part 2 - Ad-hoc Commands, Playbooks and Why one-liners aren't enough
Now, we'll start with ad-hoc commands (Ansible's one-liner mode), hit a very real wall with them, and then understand exactly why playbooks exist. Ad-hoc commands - The quick fire An ad-hoc command i
Ansible 101: Your First Ping
Just think for once, you have 10+ servers and a new user is to be created on every server, some xyz package to be installed. To do this you, you individually SSH into every server one by one to do the
From Manual Setup to IaC: Stop Clicking the AWS Console
An EC2 instance here, an S3 bucket with a specific config there, a security group someone tweaked manually six months ago. The console is stateless - it doesn't remember intent, it just shows current
