Let’s face it, tech events are thrilling, but can also be quite overwhelming. I went to AWS Student Community Day on 1st November 2025 in Tirupati. There were some great sessions all day long on different elements of cloud computing. But there was one particular session that had me totally immersed.
Senior Cloud Engineer & AWS Community Builder Keerthivasan Kannan took the stage to discuss about ‘Bridging IaC and Cloud’. He took Infrastructure as Code, a subject that could be scary, and made it consumable and logical.
I took notes and photos throughout his talk so that I could share these ideas. If you are a student or an aspiring cloud enthusiast, this blog will help you understand how you may control the cloud resources by using the code.
The Cloud Management Problem
If you’ve ever utilized a cloud provider, you undoubtedly started by logging in to the web portal. You went through menus, choose regions, set up networks and ultimately started a server. Does this sound familiar?
Manual clicking is fantastic for learning, but a nightmare in the real-world. Imagine you have to build up fifty servers, apply sophisticated security rules and reproduce that same setup for a testing team. Doing that manually is slow, frustrating and prone to human mistake.
This is where the idea of Infrastructure as Code, or IaC, comes in. You don’t click buttons, you just write simple config files that tell you exactly what you want. You provide those files to a tool and it will create the infrastructure for you.
Enter Terraform
Terraform was introduced by Keerthivasan as the IaC tool of choice in the session. But what's so special about it?
Not Just for One Cloud
You might be wondering if knowing Terraform limits you into one platform. The slides were clear: Terraform supports multi-cloud environments. It’s not AWS-only. It works with Google Cloud, Azure and dozens of other providers.
It's like a universal remote control. You don’t need a separate remote for the TV, the sound system, and the air conditioner, you use one standard remote to operate everything in your house.
The Core Workflow: Terraform Stages
Here's the thing: Terraform operates in a very predictable, logical sequence. The session broke this down into four main stages.
Init (Initialize)
Before you can build anything, Terraform needs to prepare its workspace. The init stage downloads the necessary plugins to talk to your specific cloud provider. Imagine you are about to cook a new recipe; this step is like going to the grocery store to gather all your specific ingredients.
Plan
This is your safety net.” When you run a plan, Terraform examines your code and informs you exactly what it’s going to produce, alter, or destroy. It doesn’t affect anything for now. This is like looking over the blueprint with your contractor before the concrete gets poured.
Apply
Run apply when you approve the proposal. That’s when Terraform really speaks to the cloud and makes your resources. This is when you really turn the stove on and start cooking (in our cooking example).
Destroy
When you don’t need the infrastructure anymore, the destroy command tears it all away cleanly. It’s critical for saving money on cloud bills after a project finishes.
Remembering the Past: The State File
To be fair, managing infrastructure requires a good memory. Terraform needs to know exactly what it has created so it can manage it in the future.
Tracking Changes
Terraform maintains a record of your infrastructure in what is called a “State file.” This document ties your code to the real-world resources that are running in the cloud.
Think of your state file as like a save file in a video game. When you quit the game and return tomorrow, the save file remembers which level you are on and what stuff you collected. Without that, you'd have to start from scratch.
Cloud Storage
The slides stressed that this state file should be stored in Cloud Storage, not on your local laptop. If you are working in a team , everyone has to have the same " save file " , so you do not mistakenly overwrite each other .
Keeping Things Organized: File Structure
As your cloud environment grows, your code will too. Keerthivasan shared best practices for structuring Terraform files.
Standardizing Files
You don't just write a huge wall of code . You break it down in logical files. The presentation also showed a typical directory for an EC2 (virtual server) deployment:
providers.tf: Tells Terraform which cloud to connect to (like AWS).variables.tf: Stores configurable values so you can easily change them later.locals.tf: Defines local, reusable names or tags within the module.output.tf: Displays important information after the build finishes, like the server's IP address.
Real-World Architecture
We also viewed a practical architecture diagram of a website domain (www.mbu.asia). The diagram demonstrated Terraform provisioning an S3 bucket for storage, moving traffic through a network architecture, and ultimately arriving to EC2 instances. Properly structured files make complex setups like this much easier to manage.
Building with Blocks: Modules and DRY
This is where it gets interesting. As developers, we hate doing the same work twice.
The DRY Principle
DRY is an acronym for "Don’t Repeat Yourself. The workshop taught how to do this with Locals and Variables. If you need to apply the same “Project” tag to fifty resources, you don’t write it fifty times. You define it once as a local or a variable and then refer to it everywhere.
Terraform Modules
If you find yourself writing the same code for an S3 bucket or a Security Group over and over you can construct a Module .
Think of a module like buying a cake mix. Instead than weighing out flour, sugar and baking powder every single time you want to bake, you just grab the mix, add water and you are good to go. The presentation illustrated folder structures splitting ec2, s3 and sg (security groups) into reusable modules that may be called with a few lines of code.
Advanced Magic: Variables, Loops, and Logic
To make your infrastructure truly dynamic, Terraform offers several advanced features.
Variable Validation
Sometimes you want to restrict what inputs are accepted. The slides indicated a variable block for “environment” with a strict constraint. It did validation to ensure the environment name was just "dev", "staging" or "prod". If a user inputs “testing”, Terraform will error out.
Count vs. For_each
When you want to create multiple resources, you have two main options.
Count: The slide presented an example of Web Servers creation with
count = 3. If you want exact replicas, this is great. Imagine ordering three simple pizzas the same for a party.For_each: This example shows how to create different IAM users using a map. This is best if each object has unique qualities. Imagine you are ordering meals on Swiggy for three pals, one wants a burger, the other wants pasta and the third wants a salad.
For_eachhandles those special orders well.
Dynamic Blocks
Security Groups control what network traffic is allowed in and out. The presentation included “Dynamic blocks” that automatically create multiple entrance rules. Instead of hardcoding each and every port rule, Terraform iterates over a list and dynamically constructs the rules.
Built-in Functions
Terraform is not simply resource declaration. It can conduct math and string manipulation. The functions slide was an overview of numeric, string and collection functions. One simple example provided was the ceiling function. Ceil(5.1) immediately rounds up to 6.
Conditional Statements
Finally, we looked at conditionals. The syntax shown was condition ? true_val : false_val. In other words, it is a simple decision-maker. The slide's example checked if a variable was empty. If it was empty, it assigned a default value; otherwise, it used the provided value.
Key Takeaways
If you are looking to start your journey with Terraform and IaC, here are the core lessons I picked up from the session:
Automation is Non-Negotiable: Moving away from manual console clicks to code isn’t just a “pro” move, it’s important for consistency and speed.
Trust the Workflow: Always follow
Init -> Plan -> ApplyThe “Plan” stage is your best buddy since it prevents costly or damaging mistakes from happening.The State File is Sacred: Think of your state file as a treasure map. You lose it, or corrupt it, and Terraform doesn’t know what it built anymore. Keep it on the cloud (like an S3 bucket) and not simply on your laptop.
Modules Save Time: Don't write the same code twice. Create modules that are “blueprints” of common resources like servers or databases that you can install instantaneously in new applications.
Logic Makes Infra "Smart": With variables, loops (
count and for_each) and conditional expressions your infrastructure can be flexible to new needs without you having to rebuild the entire code base.
Conclusion
AWS Student Community Day at Tirupati was an enlightening event. There were a lot of good lectures during the day on everything from AI to Security but this one on “Bridging IaC and Cloud” really caught my eye because of how practical it was.
When you first look at Infrastructure as Code it can feel like a mountain to conquer. But watching everything broken down into basic files, logical steps and reusable modules made it feel much more like playing with Lego blocks than building difficult software.
Terraform is a skill that will serve you well whether you are just starting your cloud journey or looking to scale a project. My best advice? Don’t just read about it: install Terraform, get a free-tier AWS account, and try deploying your first S3 bucket using the apply command. There’s no better way to learn than to do it!
About the Author
As an AWS Community Builder, I enjoy sharing the things I've learned through my own experiences and events, and I like to help others on their path. If you found this helpful or have any questions, don't hesitate to get in touch! 🚀
🔗 Connect with me on LinkedIn
References
Event: AWS Student Community Day Tirupati
Topic: Demystifying Terraform: Bridging the Gap Between Infrastructure and Cloud
Date: November 01, 2025
Top comments (0)