The AWS Concepts I’m Focusing on Before Building My First Cloud Project
Starting AWS as a student can feel overwhelming when there are so many services to explore. I’m trying a simpler approach: understand the core cloud concepts first, then connect them to a practical project.
Starting With the Fundamentals ☁️
When I first started exploring AWS, one thing became clear very quickly: there are a lot of services to learn.
It is tempting to jump from one service to another — EC2, S3, Lambda, databases, networking, security and so on.
But as a beginner, I think there is a better approach.
Understand the problem first, then learn the AWS service that solves it.
When I first started exploring AWS, one thing became clear very quickly: there are a lot of services to learn.
It is tempting to jump from one service to another — EC2, S3, Lambda, databases, networking, security and so on.
But as a beginner, I think there is a better approach.
Understand the problem first, then learn the AWS service that solves it.
- Compute
I want to understand how applications actually run in the cloud and when different compute options make sense.
Instead of simply memorizing service names, I want to be able to answer:
“What kind of workload do I have, and what is the simplest way to run it?” - Storage
Applications need somewhere to store data, files and other resources.
Understanding the difference between different types of storage is one of the fundamentals I want to get comfortable with before building larger projects. - Databases
Another important concept is understanding when an application needs a database and how the choice of database depends on the type of data and workload. - Networking
Networking initially looks complicated, but I’m learning that understanding the basics is essential for knowing how different parts of a cloud application communicate. - Security
This is probably one of the areas I don't want to treat as an afterthought.
Understanding permissions, authentication, and the principle of least privilege is important even when working on small projects.
🎯 My approach going forward
Rather than trying to learn every AWS service, I want to follow a simple cycle:
Learn → Understand → Build → Make mistakes → Improve
I think building even a small project can make a concept much easier to remember than simply reading about it.
I'm still at the beginning of my AWS journey, so I'm looking forward to seeing how much this approach changes my understanding over time.
For those who have already built projects on AWS: which concept gave you the biggest “now I finally understand it” moment? 👇
I'd love to learn from your experience.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article