AWS Builder Center

How I’m Learning AWS as a University Student

`Starting AWS as a university student can feel overwhelming. I’m sharing how I’m learning cloud and AI through hands-on projects, labs, and actually building things instead of just watching tutorials.`

If you’re a university student getting into AWS, you’ve probably had the same experience I did: you open AWS, see hundreds of services, and immediately wonder where the hell you’re supposed to start.
I’m studying Biomedical Engineering, but I’m also seriously getting into software, AI, and cloud because I don’t want to graduate with only the skills my degree gives me. I want to be able to actually build things.
So instead of trying to learn every AWS service at once, I’m taking a more practical approach.

1. Start With the Basics

The first thing I’m focusing on is understanding what cloud computing actually is.
EC2, S3, IAM, databases, networking, serverless, APIs — these names can sound complicated when you first see them, but you don't need to master everything immediately.
I’m trying to understand what each service is for, rather than memorizing a bunch of definitions.
For example:
EC2 → running a virtual server
S3 → storing files and data
IAM → controlling who can access what
DynamoDB → storing application data
Lambda → running code without managing a server
Once you understand the purpose, the technical details become much easier to learn.

2. Stop Just Watching Tutorials

This is probably the biggest thing I’ve learned.
Watching someone build something is easy. Building it yourself when nothing works is where the actual learning happens.
So I’m trying to spend more time doing hands-on labs and projects instead of just watching videos.
Even when I get an error, that’s still part of the process. IAM permissions, configuration errors, incorrect instance types, broken deployments — all of that is frustrating, but fixing those problems teaches you way more than watching a perfect tutorial where everything works on the first try.

3. Build Small Projects

I don't think your first AWS project needs to be some insane production-level application.
Start small.
Build something that uses a few services, understand how those services communicate, then make the next project slightly harder.
For example:
Project 1: Host a simple website.
Project 2: Add a backend API.
Project 3: Store user data in a database.
Project 4: Add authentication.
Project 5: Add an AI feature.
Eventually, you start understanding how all these different pieces fit together.

4. AI + Cloud Is Where I Want to Go

I’m especially interested in the intersection between AI and healthcare.
As a Biomedical Engineering student, this is where AWS becomes really interesting for me.
There are a lot of healthcare problems that could potentially be improved with software and AI: analyzing information, simplifying complicated medical language, processing data, building tools for patients, and helping professionals work with large amounts of information.
Cloud gives those applications somewhere to actually run.
So I’m not learning AWS just because “cloud is important.”
I’m learning it because I want to eventually use it to build things that are actually useful.

5. Certifications Aren’t the Finish Line

Certifications are useful, especially when you're a student trying to prove that you’ve been learning something.
But having a certificate doesn't automatically mean you can build.
I'd rather have:
1 certification + 3 real projects
than:
10 certifications + nothing I can actually show.
The goal is to use what I learn.

What I’m Doing Next

My plan is pretty simple:
Learn → Build → Break something → Fix it → Build again.
I’m still early in the process, and I definitely don't know everything about AWS. Honestly, that’s kind of the point.
There’s way too much to learn to wait until you “know enough” before starting.
If you're another student getting into AWS, don't let the massive list of services scare you off.
Pick one thing.
Learn it.
Build something with it.
Then move to the next thing.
You don't need to know the entire cloud.
You just need to start building in it.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article