
From Learning AWS to Teaching AWS: Lessons From a 2-Day Cloud Workshop
I recently had the opportunity to co-conduct a 2-day cloud computing workshop, “Zero to Cloud: Build Something Live.” In this post, I share what I taught, what I learned from the students, and how teaching AWS changed the way I think about cloud engineering and community knowledge-sharing.
From Learning AWS to Teaching AWS: My Experience Conducting a 2-Day Cloud Workshop
For a long time, most of my AWS journey has been about learning.
Learning how EC2 works.
Understanding IAM policies.
Deploying applications to S3.
Experimenting with Lambda and serverless architectures.
Breaking things, troubleshooting them, and trying again.
Recently, I had the opportunity to take a small step in the other direction: sharing what I had learned with others.
My friend Sabnam Khatun and I conducted a 2-day workshop, “Zero to Cloud: Build Something Live,” for BSc CSIT and BCA students at Hetauda City College.
This experience taught me something I didn't expect:
Teaching cloud computing can improve your own understanding of cloud computing.
Why We Conducted the Workshop
Cloud computing can feel overwhelming when you're just starting.
You encounter terms like:
- EC2
- S3
- IAM
- Lambda
- VPC
- Containers
- Kubernetes
- Terraform
- CI/CD
And suddenly, learning cloud becomes a question of:
“Where do I actually start?”
We wanted the workshop to provide students with a starting point.
Rather than making it purely theoretical, we wanted them to interact with AWS and understand what cloud services actually do.
The goal wasn't to turn someone into a cloud engineer in two days.
The goal was much simpler:
Give them enough understanding and hands-on exposure to continue exploring on their own.
Day 1: Building the Foundation
We started with the fundamentals of cloud computing.
We discussed:
- What cloud computing actually means
- IaaS, PaaS, and SaaS
- Public, private, and hybrid cloud
- Why organizations use cloud platforms
- Introduction to AWS
- Cloud and DevOps career paths
- The AWS Shared Responsibility Model
One thing I quickly realized was that concepts that seem obvious after working with AWS for a while aren't necessarily obvious to beginners.
For example, saying:
“EC2 provides resizable compute capacity in the cloud”
is technically correct.
But for someone completely new to cloud computing, a better explanation might be:
“AWS lets you rent a virtual computer instead of buying and maintaining a physical server.”
The second explanation creates a mental model.
And that's what I wanted the students to leave with.

Day 2: Getting Hands-On With AWS
The second day was focused much more on practical work.
We introduced students to several AWS services and demonstrated how they could be used to build something real.
Amazon EC2
We walked through the process of launching an EC2 instance.
Students learned about:
- AMIs
- Instance types
- Security Groups
- Public IP addresses
- Connecting to an instance
- Running applications on a cloud server
The important part wasn't simply showing them where to click.
We tried to explain why each component exists.
For example:
A Security Group isn't just another configuration screen.
It is effectively a virtual firewall controlling network traffic to and from the instance.
That distinction between "what to click" and "why it exists" is important when learning cloud engineering.
IAM
We also introduced AWS Identity and Access Management.
This was an opportunity to discuss one of the most important principles in cloud security:
Least privilege.
We discussed why users and applications shouldn't automatically receive administrator permissions and how IAM policies control access to AWS resources.
Even in a beginner workshop, I think security concepts should be introduced early.
It's much easier to develop good security habits from the beginning than to fix insecure practices later.
Amazon S3
We also demonstrated Amazon S3 and its object storage model.
Students uploaded files to an S3 bucket and explored how S3 can be used for storing application assets and hosting static website content.
The simple workflow looked something like:
Website Files | ▼Amazon S3 | ▼Browser
Seeing the result immediately made the concept much easier to understand.

The Most Valuable Part Was the Questions
The AWS Console wasn't actually the most interesting part of the workshop.
The questions were.
Students asked about:
- How cloud computing works
- AWS certifications
- Cloud engineering careers
- DevOps
- Which technologies to learn
- Where to start
- What skills companies actually expect
Some questions were technical.
Others were about career direction.
And that made me think about my own journey.
There are so many technologies in cloud engineering that it's easy for beginners to fall into tool collecting.
AWS → Docker → Kubernetes → Terraform → Jenkins → Ansible → GitHub Actions → ...
Learning tools isn't the same as understanding engineering.
A better approach is to understand the fundamentals first and then learn tools because you have a problem that needs solving.
Teaching Forced Me to Revisit AWS Fundamentals
One of the biggest benefits for me personally was preparation.
When you're learning something for yourself, it's easy to think:
“Yeah, I understand this.”
But when you have to explain it to another person, the standard becomes much higher.
I had to ask myself:
Can I explain this without using unnecessary jargon?
Can I explain why this service exists?
Can I give a practical example?
Can I answer the obvious follow-up question?
Those questions exposed areas where my own understanding could be improved.
And that's probably the biggest technical lesson I took from the workshop.
If you can't explain a concept clearly, you probably haven't understood it deeply enough yet.
Cloud Engineering Is More Than AWS
Another thing I wanted students to understand is that learning AWS alone doesn't make someone a cloud engineer.
Cloud engineering sits at the intersection of several areas:
Cloud | ------------------- | | | Linux Network Security | | | ------------------- | DevOps | IaC | CI/CD
AWS provides the infrastructure and services.
But engineers still need to understand operating systems, networking, security, automation, version control, and software development.
That's one reason I'm personally interested in the combination of Cloud + DevOps + DevSecOps.
Things Didn't Always Go According to Plan
Of course, working with real cloud infrastructure means things don't always go perfectly.
Configurations can be wrong.
Permissions can cause problems.
Networking can behave differently than expected.
And troubleshooting in front of a room full of students is very different from troubleshooting alone at your desk.
You don't have the luxury of spending an hour silently searching for an answer.
You need to understand the problem, communicate what's happening, and keep moving.
That experience reinforced something I have learned repeatedly while working with AWS:
Troubleshooting is a core cloud engineering skill.
Knowing the AWS console is useful.
Knowing how to investigate why something isn't working is much more valuable.
What I Learned
The workshop gave me several lessons that I want to carry forward.
1. Fundamentals matter
AWS has hundreds of services, but beginners don't need to learn all of them at once.
Understanding networking, compute, storage, identity, and security provides a much stronger foundation.
2. Hands-on experience changes everything
Reading about EC2 is different from actually launching an instance.
Reading about S3 is different from uploading an object.
The hands-on experience creates a mental connection between theory and reality.
3. Teaching improves technical understanding
Preparing to teach forced me to revisit concepts I thought I already understood.
4. Communication is a technical skill
Cloud engineers don't work in isolation.
We need to explain architectures, incidents, security issues, and infrastructure decisions to other engineers and non-technical stakeholders.
5. Community matters
Technology moves quickly.
None of us can learn everything alone.
Sharing knowledge, asking questions, writing technical content, and helping beginners are all part of building a stronger technical community.
From Learner to Contributor
I'm still learning AWS.
I'm still experimenting.
I'm still building projects.
I'm still encountering errors and searching for solutions.
But this workshop made me realize that you don't have to be an expert to contribute to a community.
If you've learned something that someone else is struggling with, you can share it.
If you've solved a problem, document it.
If you've made a mistake, explain what you learned from it.
That's how technical communities grow.
And that's something I want to continue doing as I progress further into cloud engineering.
What's Next?
This workshop has motivated me to continue both learning and sharing.
I'm currently exploring areas including:
- AWS
- Cloud Engineering
- DevOps
- DevSecOps
- Infrastructure as Code
- Serverless Architecture
- Cloud Security
I'll continue documenting what I learn through technical articles, projects, and hands-on experimentation.
Hopefully, I'll also get more opportunities to conduct workshops and contribute to the AWS community.
Final Thoughts
When we started preparing for the workshop, our goal was to teach students about cloud computing.
But after two days, I realized that I had learned quite a bit myself.
Teaching forced me to simplify concepts.
Students' questions exposed gaps in my understanding.
Troubleshooting strengthened my problem-solving skills.
And interacting with people who were just beginning their cloud journey reminded me of what it's like to learn these concepts for the first time.
I'm grateful to Hetauda City College for giving us the opportunity, to all the students who participated and asked questions, and to Sabnam Khatun for co-conducting the workshop with me.
Two days.
A lot of AWS.
A lot of questions.
A few unexpected problems.
And plenty of learning.
From learning AWS to teaching AWS — this was definitely an experience worth remembering. ☁️
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article