My First Hands-On AWS Journey: Lessons from IAM, S3 and EC2
When I started learning AWS, the first thing I noticed was how many services were available. At first, it was difficult to understand where to begin and how the different services were connected.
Instead of trying to learn everything at once, I decided to start with three fundamental services: IAM, S3, and EC2.
1. Getting Started with IAM
I started with AWS Identity and Access Management (IAM) because understanding access and permissions is important before working with other AWS resources.
One of the first things I learned was the difference between the root user and an IAM user.
I also explored:
- The principle of least privilege
The biggest lesson for me was that having access to an AWS service does not automatically mean we should give an identity full permissions. Understanding what permissions are actually required is an important part of learning AWS.
2. Exploring Amazon S3
After IAM, I moved on to Amazon S3.
S3 was easier to understand because I could immediately see the result of what I was doing. I created a bucket and experimented with uploading and managing objects.
I also explored bucket permissions and policies.
This taught me an important lesson: cloud storage is not just about uploading files; access control is equally important.
While practicing, I became more careful about making resources publicly accessible. It is important to understand exactly who can access a resource before changing its permissions.
3. Launching My First EC2 Instance
My next step was Amazon EC2.
Launching an EC2 instance was probably one of the most interesting parts of my beginner journey because it helped me understand what a cloud server actually feels like to use.
I explored concepts such as:
- Starting and stopping instances
Security groups were particularly interesting because they act as a virtual firewall for the instance.
For example, if I want to connect to an EC2 instance remotely, I need to understand which inbound traffic should be allowed.
4. A Lesson About AWS Costs
One thing I did not want to ignore while learning AWS was cost management.
When experimenting with cloud services, it is easy to create a resource and forget about it.
I learned that beginners should pay attention to:
- Stopping or deleting resources when they are no longer needed
Setting up a budget and monitoring usage gave me more confidence to experiment with AWS.
5. What These Three Services Taught Me
These services helped me understand three basic building blocks of cloud computing:
IAM → Who can access resources?
S3 → Where can I store data?
EC2 → Where can I run applications?
Seeing these concepts separately made AWS easier to understand.
More importantly, I realized that learning cloud computing is not just about memorizing service names. It is about understanding why a service is used and how it fits into a real system.
6. What I Want to Learn Next
I am still at the beginning of my AWS journey.
My next areas to explore are:
- Building small cloud projects
I want to move from simply following tutorials to building and troubleshooting things myself.
Final Thoughts
Starting AWS can definitely feel overwhelming in the beginning. There are hundreds of services, and it is tempting to jump between them.
For me, focusing on a few core services first made the learning process much easier.
My advice to anyone starting AWS would be:
Learn one service, understand why it exists, practice it yourself, and then move to the next one.
Even small hands-on experiments can teach things that are difficult to understand from theory alone.
This is only the beginning of my AWS journey, and I’m looking forward to learning more, building projects, making mistakes, and sharing what I learn along the way.
What was the first AWS service you worked with when you started learning cloud?
Loading article