AWS Builder Center
5 AWS Services I’m Learning First as a Career Changer

5 AWS Services I’m Learning First as a Career Changer

The five AWS services I’m learning first as a career changer, including EC2, S3, IAM, Lambda, and VPC, plus why each one matters.

AWS Learner | Software Engineering Student | Cloud & Infrastructure
When I first started learning AWS, the hardest part was not understanding what cloud computing was. It was figuring out where to start.
AWS has a massive number of services, and as a beginner, it is easy to look at the console and feel like you accidentally opened the control panel for a spaceship.
Instead of trying to learn everything at once, I decided to focus on a small group of core services that show up repeatedly in AWS training, real-world environments, and certification material.
Here are the five AWS services I am focusing on first.

1. Amazon EC2

Amazon EC2 is one of the first AWS services that made sense to me because I already had experience running virtual machines and servers in my homelab.
EC2 lets you create virtual servers in the cloud.
Instead of buying physical hardware, installing an operating system, configuring networking, and maintaining the machine yourself, you can launch a virtual server in AWS in a few minutes.
You can choose things such as:
  • Operating system
  • CPU and memory
  • Storage
  • Network configuration
  • Security settings
One thing I am trying to understand better is not just how to launch an EC2 instance, but how all the surrounding pieces work together.
That includes security groups, SSH access, IAM roles, storage, and networking.
Launching the server is the easy part. Understanding how to configure it securely is where the real learning starts.

2. Amazon S3

Amazon S3 is AWS object storage.
At first, I thought of S3 as basically cloud file storage, but there is much more to it.
S3 can be used for:
  • Backups
  • Website assets
  • Logs
  • Application data
  • Static websites
  • Data lakes
  • Disaster recovery
One of the things I like about S3 is that it introduces several important cloud concepts at the same time.
You start learning about permissions, encryption, versioning, lifecycle policies, and access control.
Even something simple like uploading a file to a bucket can turn into a useful security lesson once you start asking who should be able to access it and how that access should be controlled.

3. AWS IAM

IAM might not be the most exciting service when you first start learning AWS, but I think it may be one of the most important.
IAM stands for Identity and Access Management.
It controls who can access AWS resources and what they are allowed to do.
Some of the core concepts include:
  • Users
  • Groups
  • Roles
  • Policies
  • Permissions
  • Least privilege
The principle of least privilege is something I keep seeing repeatedly.
The basic idea is simple: give users and services only the permissions they actually need.
If an application only needs to read files from one S3 bucket, it should not have permission to delete every resource in the AWS account.
Security mistakes in the cloud can become expensive very quickly, so IAM is one area I want to understand well instead of just memorizing enough to pass an exam.

4. AWS Lambda

Lambda is one of the AWS services that really demonstrates how different cloud computing can be from traditional infrastructure.
With Lambda, you can run code without managing the underlying server.
You upload your code, configure when it should run, and AWS handles the infrastructure behind it.
For example, a Lambda function could run when:
  • A file is uploaded to S3
  • An API request is received
  • A scheduled event occurs
  • A message enters a queue
Coming from a background where I am used to thinking about servers, virtual machines, Docker containers, and operating systems, serverless computing changes the way I think about applications.
Instead of asking, “What server should this run on?” you can start asking, “What event should trigger this code?”
That is a completely different mindset.

5. Amazon VPC

Amazon VPC is the service I expect to spend a lot of time learning because networking connects almost everything else together.
VPC stands for Virtual Private Cloud.
It allows you to create an isolated network inside AWS.
Within a VPC, you start working with concepts such as:
  • Subnets
  • Route tables
  • Internet gateways
  • Private and public IP addresses
  • Security groups
  • Network ACLs
This is one of the areas where my homelab experience helps.
Working with virtual machines, DNS, firewalls, Docker networks, and remote access has already shown me how important networking is.
AWS changes the tools, but many of the underlying concepts are familiar.

Why I’m Starting With These Five

I am focusing on EC2, S3, IAM, Lambda, and VPC because they connect to many of the larger AWS concepts I want to understand.
Together they cover:
Compute → EC2
Storage → S3
Security → IAM
Serverless → Lambda
Networking → VPC
Once those foundations make sense, I think learning additional AWS services will become much easier.
Instead of seeing hundreds of unrelated product names, I can start understanding where each service fits into an architecture.

My Next Step: Build Something

The next goal is to stop treating AWS as something I only study and start using it to build small projects.
A few projects I am considering include:
  • Hosting a static website with S3
  • Deploying a Linux server with EC2
  • Building a simple serverless API with Lambda
  • Creating a VPC with public and private subnets
  • Configuring IAM roles using least privilege
  • Sending application logs into AWS monitoring tools
None of these projects need to be huge.
The point is to build something, break something, troubleshoot it, and understand why it works.
That is usually where the best learning happens.

Final Thoughts

AWS can feel overwhelming because of how many services exist, but I am starting to realize that I do not need to learn everything at once.
I just need to understand the foundations and keep building from there.
For now, these five services are my starting point.
If you are learning AWS too, what service did you learn first, and which one helped cloud computing finally start making sense?
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