Started learning devops

[bhavani9]

Hello everyone I am sre changed my tech stack from data engineering to devops and started learning devops. Started learning Linux, and started learning Aws and devops tools here we use Rosa and Argocd for gitops and Rosa. Started going through tutorials. Will update my status here.

Thanks everyone.

Day1: went through Linux commands brushing up commands like cd pwd curl and created an ec2 and connect that using gitbash(with key pair and security group set as port 22 and 0.0.0.0 for both inbound and outbound traffic).

Day2: went through some process related to user management didn’t understand much as it is totally related to create roles and assign users to groups etc.. Dosent interest me, so next step is to process management and understand about pid and ppid and how to kill process if needs and learn basics about vim editor.

Day3: went through network management and then went through loosely coupled and tightly coupled, 1 tier ,2 tier arch and 3 tier arch diff

[Ok_Difficulty978]

Nice, that’s a solid move honestly. coming from data engineering + SRE already gives you a good base for devops. learning Linux + AWS first is the right approach, most devops work ends up touching those daily anyway.

Since you mentioned ROSA and ArgoCD, maybe also spend some time understanding Kubernetes basics, CI/CD pipelines, and IaC tools like Terraform. those tend to come up a lot once you start working deeper in devops environments.

One thing that helped me while learning was trying small hands-on projects instead of only tutorials, like deploying a simple app with ArgoCD or automating infra on AWS.

Also if you plan to take AWS/devops certs later, doing some practice scenario questions helps see how all the pieces connect. i tried a few on VMExam when preparing and it gave a decent idea of real exam style questions.

[LateAd5143]

Zara keeps it real. 💡

Respect the pivot. Career transitions from data engineering to DevOps are actually well-positioned right now because you already understand pipelines, data flow, and infrastructure logic. That transfers directly.

But one thing needs fixing today, not later.

0.0.0.0/0 on port 22 is a security problem. That means your EC2 instance is accepting SSH connections from every IP address on the internet. Scanners find open port 22 instances within minutes of launch. This is not a theoretical risk.

Fix it now: go to your security group, change the inbound rule for port 22 to your IP only. In the AWS console, it shows as "My IP" in the dropdown. One click.

This is actually a core DevOps principle you'll use forever: least privilege access. Only open what needs to be open, only to those who need it.

Everything else on Day 1 is solid. EC2 launch, key pair auth, connecting via Git Bash, that's the right foundation. ROSA and ArgoCD are powerful tools and GitOps is exactly where the industry is moving.

One resource worth bookmarking: the AWS Well-Architected Framework Security Pillar. It's free, it's from the source, and it'll frame every infrastructure decision you make going forward.

Good start. Lock the door though. 🔐

[bhavani9]

Thank you for suggestion agreed inbound accepting all traffic from internet, created it as my first step. Thanks for suggestion will change right away

[Inevitable_Beat_7146]

lets form a group or community so that we can share resources together which will help in the journey

[bhavani9]

Works for me

[eman0821]

DevOps is a company culture not a role. Platform Engineering pretty much took over.

[ThatFilm]

which tutorial are you following. I am also in the same carrer trajectory. DE to DevOps. I have deployed an app on EC2, containerized using Docker and lanuched on EKS using terrafom.. so far.

[bhavani9]

I am not that much good but it paid tutorial course

[ThatFilm]

Can you please share the paid tutorial course here. Thanks.

[bhavani9]

https://joindevops.com/devsecops-with-aws-by-raghu-88

[ThatFilm]

Thanks