AWS Builder Center
How I’m Building an AWS Learning Roadmap as a Career Changer

How I’m Building an AWS Learning Roadmap as a Career Changer

A career changer’s practical AWS learning roadmap, from Cloud Practitioner fundamentals to hands-on projects, CloudOps, and security.

AWS Learner | Software Engineering Student | Cloud & Infrastructure

Starting From the Beginning

Moving into cloud computing can feel overwhelming.
AWS alone has hundreds of services, multiple certification paths, labs, learning plans, documentation, and enough acronyms to make alphabet soup look organized.
When I started looking seriously at AWS, I realized that simply saving interesting courses was not the same thing as having a learning plan.
I needed an order.
My goal is not to memorize every AWS service. I want to build a foundation that helps me understand how cloud systems actually work and eventually apply those skills to system administration, cloud operations, cybersecurity, and software engineering.
So I started building my own AWS roadmap.

Step 1: Learn the AWS Fundamentals

My first major step was completing AWS Cloud Practitioner Essentials.
This introduced concepts such as:
  • AWS Regions and Availability Zones
  • Compute services
  • Storage
  • Networking
  • Identity and access management
  • Databases
  • Security
  • Monitoring
  • Pricing and support
The biggest value was not memorizing individual services.
It was learning how AWS is structured.
For example, instead of seeing Amazon EC2 as just another AWS product, I started thinking of it as a virtual server that can be created, configured, secured, monitored, and connected to other cloud resources.
That connection to concepts I already understood made AWS much easier to learn.

Step 2: Build Things Instead of Only Watching Videos

Training videos are useful, but cloud computing makes much more sense when you actually deploy something.
Even small projects help.
Some examples I want to continue building include:
  • Creating and securing an S3 bucket
  • Hosting a simple static website
  • Launching an EC2 instance
  • Configuring security groups
  • Creating IAM users and roles
  • Using AWS CLI commands
  • Monitoring resources with CloudWatch
  • Creating backups
  • Experimenting with VPC networking
The goal is not to create a massive production environment.
The goal is to understand what happens when the pieces interact.
Reading about security groups is one thing.
Launching an EC2 instance and discovering that your application cannot be reached because the correct port is not allowed teaches the concept much faster.

Step 3: Move Toward Solutions Architecture

After learning the fundamentals, I want to develop a broader understanding of how AWS services fit together.
That is why Solutions Architect material is an important next step in my roadmap.
Solutions architecture forces you to think beyond individual services.
You start asking questions such as:
  • Where should this application run?
  • Where should its data be stored?
  • How should users connect to it?
  • What happens if a server fails?
  • How should access be controlled?
  • How do we reduce costs?
  • How do we design for recovery?
Those questions are useful even if your eventual job title is not Solutions Architect.
They teach systems thinking.

Step 4: Learn Cloud Operations

One of my strongest interests is system administration, so the AWS CloudOps Engineer learning path is especially relevant to me.
Cloud operations connects traditional systems administration skills with cloud infrastructure.
That includes areas such as:
  • Monitoring
  • Logging
  • Automation
  • Troubleshooting
  • Networking
  • Configuration management
  • Reliability
  • Backup and recovery
  • Incident response
I already enjoy working with Linux servers, Docker, networking, monitoring, and self-hosted services, so CloudOps gives me a way to extend those skills into AWS.
Rather than treating cloud computing as something completely separate from traditional IT, I see it as the next layer.
The concepts are often familiar.
The implementation changes.

Step 5: Add Security on Top of the Foundation

Cybersecurity is another long-term goal, but I do not want to jump directly into advanced cloud security without understanding the infrastructure being protected.
My plan is to build the AWS foundation first, then delve deeper into security topics.
That includes areas such as:
  • IAM
  • Least privilege
  • Encryption
  • Logging
  • Network security
  • Threat detection
  • Security monitoring
  • Incident response
  • AWS security services
Security makes much more sense when you understand the systems underneath it.
Trying to secure infrastructure you do not understand is like trying to install locks before you know where the doors are.

My Current AWS Learning Order

The roadmap I am currently following looks roughly like this:
  1. AWS fundamentals
  1. Hands-on beginner projects
  1. Solutions Architect concepts
  1. Cloud operations
  1. AWS security
  1. Larger projects combining multiple services
I expect that order to change as I learn more.
That is fine.
A roadmap should provide direction, not become a prison sentence.

Connecting AWS With a Homelab

One thing that has helped me is comparing AWS services with systems I already use in my homelab.
For example:
Homelab Concept
AWS Concept
Virtual machine
Amazon EC2
Local storage
Amazon EBS
Object storage
Amazon S3
Firewall rules
Security Groups
Local network
Amazon VPC
User permissions
AWS IAM
Server monitoring
Amazon CloudWatch
DNS management
Amazon Route 53
The technologies are not identical, but the comparisons provide useful mental models.
That makes unfamiliar AWS terminology much easier to understand.

Avoiding the Certification Trap

Certifications are part of my plan, but I do not want certification preparation to become the entire goal.
It is possible to memorize enough information to answer certification questions without being comfortable actually building anything.
I want both.
The certification provides structure and validates knowledge.
Projects provide experience.
Ideally, each reinforces the other.
If I learn about S3 during certification training, I want to create a bucket.
If I learn about IAM policies, I want to experiment with permissions.
If I learn about monitoring, I want to configure monitoring.
That turns abstract knowledge into something I can actually use.

What I Have Learned So Far

The biggest lesson has been simple:
You do not need to learn AWS all at once.
Pick a foundation.
Build something.
Break something.
Figure out why it broke.
Fix it.
Then add another layer.
AWS becomes much less intimidating once the individual services stop looking like hundreds of unrelated products and start looking like building blocks for solving familiar infrastructure problems.
For anyone else moving into cloud computing from another career, I would recommend that approach.
Do not try to become an expert in every AWS service.
Build a solid foundation, choose a direction, and keep expanding from there.
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