AWS Builder Center

Builder Center

I Know AWS Services. But What Should I Build? 🚀

Learning AWS is more than memorizing services—it’s about understanding how they work together to solve real-world problems. In this article, I share my journey from learning individual AWS services to thinking about architecture, security, deployment, monitoring, Docker, Terraform, and Kubernetes. I also explore how project-based learning can help beginners move from **“I know AWS”** to **“I can build with AWS.”** ☁️🚀

When I started learning AWS, I followed what I thought was the right approach.
I learned EC2, S3, IAM, VPC, Lambda, RDS, CloudWatch, and many other services.
I watched tutorials.
I completed labs.
I made notes.
And I could explain what each service does.
But eventually, I faced a question that many beginners might relate to:
“I know AWS… but what should I actually build?”

The Problem Isn't Learning AWS

There are thousands of tutorials explaining individual AWS services.
For example:
EC2 → Run applications
S3 → Store files
Lambda → Run code without managing servers
RDS → Managed databases
IAM → Manage access
VPC → Networking
CloudWatch → Monitoring
But a real application doesn't use these services independently.
The difficult part is understanding:
How do I combine them to solve an actual problem?
That's where I think the biggest learning gap exists.

From Services to Solutions

Suppose I want to build a file-processing application.
Instead of learning five AWS services separately, I could build something like:
User → S3 → Lambda → DynamoDB → SNS
For example:
  1. A user uploads a file to S3.
  2. S3 triggers a Lambda function.
  3. Lambda processes the file.
  4. DynamoDB stores the processing information.
  5. SNS sends a notification.
Now I'm not just learning five AWS services.
I'm learning how they communicate and work together.
And that's a completely different kind of learning.

What If AWS Learning Followed This Approach?

Imagine having a project roadmap like:

🟢 Beginner

Build: Serverless File Processor
Learn:
  • S3
  • Lambda
  • DynamoDB
  • SNS
  • IAM

🟡 Intermediate

Build: Scalable Web Application
Learn:
  • VPC
  • EC2
  • RDS
  • Load Balancer
  • Auto Scaling
  • CloudWatch

🔵 Advanced

Build: Containerized Application
Learn:
  • Docker
  • ECR
  • ECS/EKS
  • Terraform
  • CI/CD
  • Monitoring
  • Security
Instead of asking:
“Which AWS service should I learn next?”
I'd be asking:
“What should I build next?”
That shift could make learning much more meaningful.

What I Want to Learn From Every Project

For me, a good cloud project shouldn't just provide a GitHub repository or a list of AWS services.
I'd want to understand:
1. What problem are we solving?
2. Why did we choose these AWS services?
3. What does the architecture look like?
4. How does data move through the system?
5. How is the application secured?
6. What happens if something fails?
7. How would we scale it?
8. How would we monitor it?
9. How could we reduce its cost?
And most importantly:
Could I explain the project in an interview or technical discussion?

The Difference Between a Lab and a Project

A lab might teach me:
“Create an S3 bucket and upload an object.”
A project should make me think:
“Why am I using S3 here instead of another storage solution?”
That difference is important.
Labs are excellent for learning individual concepts.
Projects teach us how to make decisions.
And I think decision-making is one of the most important cloud skills to develop.

What I'm Trying to Do Now

I'm trying to change my learning approach.
Instead of:
Learn AWS service → Make notes → Move to next service
I'm experimenting with:
Problem → Architecture → AWS services → Build → Break → Debug → Monitor → Improve
This approach also naturally introduces other technologies.
For example:
AWS + Docker + Terraform + Kubernetes + Git + CI/CD
Instead of learning them as completely separate topics, I can understand where each technology fits into the bigger picture.

My Question to the AWS Community

I'd love to hear from other builders.

If you were starting your AWS journey again, what is the ONE project you would build first?

Not a tutorial.
Not a basic “launch an EC2 instance” lab.
A real project that teaches useful cloud skills.
And if you've already built several AWS projects:
Which project taught you the most, and what did you learn from it?
Share your project or idea in the comments. 👇
Maybe we can create a list of practical AWS projects that other students and beginners can learn from.

Final Thought

I don't think the goal of learning AWS should be:
“I know 30 AWS services.”
A better goal might be:
“Give me a problem, and I can design and build a cloud-based solution.”
That's the skill I'm working toward.
What are you building on AWS? ☁️🚀
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