Beyond the Classroom: Building with Kiro, AWS, and the Cloud
A hands-on Kiro session with the AWS Student Builder Group at UICT Kampala revealed a bigger lesson: many students have the ability to build, but lack exposure to emerging technologies. By creating portfolio websites with Kiro and hosting them on Amazon S3, students experienced modern software development and cloud computing firsthand. This article explores why continuous learning, experimentation, and tech communities are essential to developing the builder mindset.
We Built a Website in Minutes. The Real Lesson Was Much Bigger.
What a hands-on Kiro session taught me about the technology exposure gap among students and why continuous learning matters more than ever.
The moment that made me think differently
A student walks into a technology session expecting to learn about another new tool.
A few minutes later, they have a working website.
That was the experience during our recent hands-on session with the AWS Student Builder Group at UICT Kampala, where we explored Kiro and used it to turn ideas into working software.
The goal was simple: introduce students to Kiro, an agentic AI IDE from AWS, and let them experience a modern, spec-driven approach to software development.
Rather than spending the entire session presenting slides, we wanted students to build.
And they did.
Students explored Kiro, described what they wanted to create, worked through the development process, and built portfolio websites that they could actually deploy. We then took the experience one step further by hosting the websites using Amazon S3, giving students a glimpse of what it means to move from an idea on a laptop to something accessible on the internet.
But while watching students build, I realized something much bigger.
The biggest challenge is not that students cannot build.
It is that many students simply have not been exposed to what they can build with.
From “I can code” to “I can build”
There is an important difference between knowing how to program and knowing how modern software is actually built.
A student may know HTML, CSS, JavaScript, Python, Java, or another programming language. They may have completed assignments and even built a few academic projects.
But then you introduce concepts such as cloud computing, object storage, serverless architectures, AI-assisted development, infrastructure as code, APIs, containers, or agentic AI and suddenly the landscape looks very different.
This is not necessarily because students lack intelligence or ambition.
Sometimes they simply have not encountered these technologies yet.
That is why exposure matters.
During the session, Kiro gave students a practical way to experience a modern development workflow. Instead of simply prompting an AI to generate code and hoping for the best, Kiro introduces a more structured process: requirements → design → tasks → code. The idea is to make the reasoning behind the software part of the development process rather than treating code generation as the entire workflow.
For someone encountering this approach for the first time, that can change how they think about software development.
And that is exactly what technology communities should help create.
The cloud is not something to learn “later”
One of the most important observations from the session was how unfamiliar cloud computing still is to many students.
For some, AWS can initially sound like something reserved for large companies, experienced engineers, or people already working in the industry.
But the cloud becomes much less intimidating when you actually use it.
Take our simple portfolio website.
A student can create a website locally.
That is already useful.
But then comes the question:
How do I make this website available to someone else?
That question opens the door to cloud computing.
In our session, students used Amazon S3 to host their websites. Suddenly, a concept that may have previously existed as a definition in a classroom or YouTube video became something tangible: I built this, and I can put it online.
That transition from hearing about technology to using technology is where a lot of learning happens.
Kiro was the tool. Building was the lesson.
It would be easy to make this article about Kiro.
And Kiro was certainly an important part of the session.
Kiro is an agentic AI IDE designed around a spec-driven development workflow. It can transform natural-language prompts into structured requirements, design documents, implementation tasks, and eventually code. The platform also includes features such as steering files, hooks, and integrations through MCP and other tools.
But the deeper lesson was not “everyone should use Kiro.”
The lesson was:
Students need to experiment with the tools changing the way technology is built.
Today it is agentic AI.
Tomorrow it may be something else.
The specific tool will change.
The mindset should not.
Don't wait until graduation to discover the industry
There is a dangerous habit among students:
«“I will learn that when I get a job.”»
Cloud computing?
I'll learn it when I get hired.
AI?
I'll learn it when I need it.
DevOps?
I'll learn it after graduation.
New development tools?
I'll worry about them later.
The problem is that technology does not wait for graduation.
The industry continues moving while students are still completing assignments.
By the time a student enters the job market, the technologies they assumed they would learn “later” may already be part of the baseline expectations.
This does not mean students need to learn every new technology.
That would be impossible.
It means students need to develop the ability to discover, evaluate, experiment with, and learn new technologies continuously.
That is a much more valuable skill.
You don't need to master everything. You need to stay curious.
One mistake students make when they see new technology is thinking:
«“There is too much to learn. Where do I even start?”»
You do not need to become an expert in every technology.
Start small.
If you hear about cloud computing, create something on the cloud.
If you hear about AI agents, experiment with one.
If you hear about serverless applications, build a small project.
If you hear about a new developer tool, try it on something you already know how to build.
The goal of exploration is not immediate mastery.
It is exposure.
Exposure creates curiosity.
Curiosity creates experimentation.
Experimentation creates understanding.
And understanding eventually becomes skill.
This is why communities matter
One of the biggest reasons we run sessions like this through the AWS Student Builder Group at UICT is because learning technology alone can be difficult.
You can watch hundreds of tutorials and still struggle to know what to build.
You can read documentation and still wonder how everything fits together.
You can hear people talk about cloud computing, AI, DevOps, or cybersecurity and still feel like these technologies are happening somewhere far away from you.
A community changes that.
You see someone beside you building.
You ask questions.
Someone helps you troubleshoot.
You discover a tool you had never heard of.
You share what you built.
Then someone else becomes curious.
That cycle is powerful.
AWS Student Builder Groups are designed around this idea: students coming together to explore, create, and grow through hands-on experiences and community.
The objective is not simply to produce students who know AWS commands.
It is to develop builders.
Your first cloud project does not have to be complicated
If you are a student reading this and you have never used AWS before, don't start by trying to build the next billion-dollar platform.
Start with something small.
Build a portfolio.
Host a static website.
Create a simple API.
Deploy a small application.
Experiment with storage.
Try a serverless function.
Connect an application to a cloud service.
The important thing is that you move from:
“I have heard about AWS.”
to:
“I have built something with AWS.”
That difference matters.
Our Kiro session demonstrated this beautifully. What started as an introduction to a new development tool ended with students having something tangible they could show, improve, and continue building.
The first project may be simple.
That is okay.
Simple projects are often the beginning of much bigger ones.
What I want students to take away
If there is one thing I hope students take away from this session, it is this:
Don't let your university syllabus define the limits of your technology education.
Your degree gives you foundations.
Your curiosity determines how far you take them.
Follow technologies that interest you.
Join communities.
Attend workshops.
Build projects.
Ask questions.
Read documentation.
Participate in hackathons.
Connect with people who are already building.
And most importantly, keep learning.
You do not have to know everything today.
But you should be willing to discover what you don't know.
The future belongs to builders
Technology is changing quickly.
AI is changing how software is created.
Cloud computing is changing how software is deployed and operated.
New tools are changing how developers work.
The students who thrive in this environment will not necessarily be the ones who memorized the most technologies.
They will be the ones who can look at something new and say:
“I don't know this yet. Let me learn it.”
That is the builder mindset.
Our Kiro session was one small step toward creating that mindset at UICT.
We came together to learn a tool.
We left with something more valuable: a reminder that technology becomes less intimidating when you stop watching from the outside and start building.
So don't wait for the future to teach you what is already here.
Explore it.
Build with it.
Learn with others.
And keep building.
---
Keep building
If you're a student interested in cloud computing, AI, and emerging technologies, connect with the AWS Student Builder Group at UICT Kampala and keep learning alongside other student builders.
The next technology that changes your career might be one you have not discovered yet.
Go discover it.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article