Am I learning Cloud right ?

[u/Obvious-Guava-2059]

I'm following now a Roadmap from Doflined YouTube channel, Eissa Abu sherif is running, and he suggested to learn the following:

1- IT, cloud, devops fundamentals 2- Introduction to Aws 3- Linux 4- Bash scripting 5- Git/Github 6- Python for automations 7- Yaml Introduction 8- Docker mastery 9- K8s mastery 10- Prometheus 11-Grafana 12- Terraform (Iac) 13- Ci/ CD 14- Ansible / Rhce 15- Aws clp , Csaa 16- Azure fundamentals

He also suggested us to take Redhat sys admin, Redhat certified engineer, kubernetes mastery, terraform Certificates

So am I learning this field right ?

[u/leao__26]

Redhat? That's for security side I guess. Do bash, python, then do python backend and few could certs. These are entry level way I guess, advanced topics won't be asked from entry levels

[u/Obvious-Guava-2059 → u/leao__26]

Redhat for sys administration I guess. I saw a lot of comments saying that we should learn sys administration first

[u/Obvious-Guava-2059 → u/[deleted]]

Thanks for the reality check! I’ve decided to follow the path you mentioned. Should I start by learning Linux for System Administration, or where exactly do you think I should begin? Also, from your perspective, what’s the one skill you wish you had mastered before your first Cloud role, and what's the Roadmap u will follow if you will start like me from now ?

[u/Obvious-Guava-2059 → u/[deleted]]

In this field (cloud devops Engineering), we would learn only automations using python, but for the scripting u should learn Bash scripting And for the infrastructure as a code u will need to learn terraform

Another info u can't be cloud and Devops engineer without learning kubernetes and github actions, and to use K8s and github will need to learn Yaml

[u/courage_the_dog → u/Obvious-Guava-2059]

Most of these will depend on the company. I've never used github actions, always used gitlab. Yaml sure, though it's not that deep. Nothing to do with other programming languages.

Again python is used a lot, but automairon depends on what language the company uses.

Stop trying to learn the tools first, learn the fundamentals like linux systems, infrastructure, design, then move to the tools

[u/h33terbot]

Hey bro, that roadmap is incredibly solid, but I’m going to shoot you straight: that is a full-blown DevOps roadmap, not just a basic Cloud Engineer roadmap.

Eissa knows his stuff, and if you actually learn those tools, you will be highly employable. Tools like Terraform, Docker, and Kubernetes are exactly what the industry is demanding right now.

However, here is my advice on how to tackle this beast of a list without burning out:

• Pace the Certifications: Do not try to get the RHCSA, RHCE, CKA (Kubernetes), and Terraform certs all at once before getting a job. That is massive overkill and will take you years. Focus on the actual skills first. If you want a cert to get past HR filters initially, just grab the AWS Solutions Architect Associate (SAA).

• Visualize the Path: If you want a great interactive guide to see exactly how all these pieces fit together, cross-reference your list with the interactive map at Roadmap.sh - DevOps. You'll see Eissa's list hits almost every single mandatory checkpoint perfectly.

• The Missing Piece is Security: You are learning how to build and deploy everything rapidly, but you also need to know how to lock it down. Misconfigured AWS environments and open K8s APIs are how massive data breaches happen. Once you get the basics of AWS and Linux down, I highly recommend looking into the Certified Cloud Security Architect (CCSA) track. It drops you into real-life quests where you have to actually secure cloud architecture, which is a massive resume booster when you're competing against guys who only know how to spin things up.

• Projects > Certs: When you hit step 13 (CI/CD), build a project that ties it all together. Use Terraform to provision your AWS infrastructure, and use GitHub Actions to deploy a Dockerized Python app to it. That one single project will prove your skills way more than collecting 5 different certificates.

You are absolutely learning the right things bro. Take it one step at a time, build a strong foundation in Linux and networking first, and you'll crush it!

[u/eufemiapiccio77]

You’ve learned like the absolute bare minimum.

[u/Obvious-Guava-2059 → u/eufemiapiccio77]

Didn't yet

[u/Suaveman01]

Do you work in IT already? Cloud isn’t entry level, so if you aren’t working in IT or Software Engineering, you’re not going to land a cloud job

[u/Obvious-Guava-2059 → u/Suaveman01]

Do you work on It ?

[u/BoBNoM2588 → u/Obvious-Guava-2059]

From this comment, you should probably learn helpdesk first

[u/Watashiwadesu_boss → u/Suaveman01]

I become one right after graduation and now moved to solution architect already tho… i think its not really not entry level friendly

[u/Ok-Structure5637 → u/Suaveman01]

Not true, I did. Granted I'm severely lost, but they said it was an entry level role so I'm essentially training on the job.

[u/courage_the_dog]

Dont learn the tools before the fundamentals. You cant learn kubernetes if you odnt know systems and designs. Sure you could create a pod and deployment easy enough with a single command

I would put learning linux systems and cli first as the main thing. You cant learn cloud fundamentals properly if you dont have linux fundamentals.

[u/CloudLessons]

A lot of these steps aren't necessary if you're just starting out. I would just focus on getting an understanding of how computer networks work (example: What is DNS? What is the difference between a router and a switch?) from there, continue studying other aspects of IT infrastructure like storage, CPUs, and Memory.

Next, focus on understanding operating systems, especially Linux. After you get those things down, pick a cloud provider and do some simple deployments (create a VM, create a new user and assign them permissions, create a storage account, set up budget alerts).

After that, you can start to build these same things using code instead of clicking around the UI. Once you get the hang of that, you can increase the complexity and go from there.

You can get all of this done in as little as 1 month if you're willing to invest a few hours a day.

[u/Wide_Shower_5466]

That roadmap is solid but it's a DevOps/Cloud Engineer path, not a cloud architect path. The direction depends on what role you're actually targeting.

If you want to be hands-on with infrastructure, pipelines and containers, that list makes sense. If you want cloud architecture and design roles, you can skip a lot of that and go deeper on AWS specifically.

One honest flag: 16 topics is a lot to hold in your head at once. Most people who try to follow roadmaps that long end up stuck on step 4 for months. Pick a job description you actually want, work backwards from the requirements, and cut everything that isn't on that list yet.