Day 12/90 | Reviewing Linux & AWS Fundamentals

12 months ago, I didn't know what SSH was. Today, I work with Linux servers, configure cloud infrastructure on AWS, and build deployments using Docker and Kubernetes. I didn't follow a perfect roadmap. Most of my learning came from building, breaking, and fixing things. Here's what actually helped me improve: Don't rely only on tutorials. Try to build something alongside them. Break things in a safe environment and understand how to fix them. Document what you build - it becomes your portfolio over time. → Focus on Linux fundamentals before moving into complex tools. Your first project doesn't need to be perfect. It just needs to exist. The gap between knowing concepts and actually doing DevOps comes down to hands-on practice. If you're starting out, you don't need everything at once. A small server and consistency can take you far. Curious to know - what helped you most when you were starting in tech? #DEVOPS #LINUX #K8S #DOCKER #AWS #EKS #IAM #CICD #TERRAFORM #GIT #CONTAINERS

🚀 Day 6 & 7/60 – #60DaysToCloud This days , instead of jumping to new topics, I focused on revising what I already learned. 📌 Week 0 Goal: Linux • Git • Networking • Cloud Basics 🔁 Why Revision? I realized that just learning new concepts daily isn’t enough. Without revision, it’s easy to forget important details. So I went back and practiced the same topics again. 🔹 What I revised: 💻 Linux Basics Commands: ls, cat, pwd, cd File permissions and symbolic links (ln -s) 🌿 Git & GitHub git add, git commit, git push, git pull Branching basics, merge vs rebase Working directory vs staging vs repository 🌐 Networking Basics IP Address, DNS, Ports How a request travels from client to server ☁️ Cloud Basics IaaS, PaaS, SaaS Public, Private, Hybrid Cloud 💡 What I learned from revision: Concepts became much clearer I understood the “why” behind commands I feel more confident applying what I learned Revisiting topics helps build strong fundamentals and avoids confusion later when concepts become more advanced. 🎯 Next Week Goal: 1. Start AWS  2. Learn EC2 (virtual servers) 3. Practice connecting to cloud instances using SSH 4. Know what regions, AZs, compute, storage, networking, and IAM are 5. Have deployed a static site once Small steps every day lead to big progress 🚀 #60DaysToCloud #LearningInPublic #CloudComputing #DevOps #Linux #Git #learningjourney

🚀 Day 4 of my Bootcamp Exlearn Technologies Technologies! 🚀 Another power-packed session with Prashant Gavate sir! Today, we dived deep into the backbone of modern technology: Linux 🐧 If you’re aiming for a career in Cloud or DevOps, you simply can’t ignore Linux. Here’s why it’s a game-changer: 🔹 Key Takeaways: 🔸 Foundation of Cloud – Most cloud platforms like AWS, Azure, and GCP run on Linux. Understanding Linux is essential to manage cloud environments effectively. 🔸 DevOps Essentials – Tools like Docker, Kubernetes, and Ansible are built on Linux, making it a core skill for automation and deployment. 🔸 Understanding OS – Learned how Linux acts as an interface between user and hardware, managing resources like CPU, memory, and storage. 🔸 Server vs Client OS – Difference between server-side and client-side operating systems and their real-time usage. 🔸 Open Source Power – Linux is free, flexible, and widely used across industries. 🔸 Real-World Insight – Around 90% of servers in the tech world run on Linux OS. Huge thanks to Prashant Gavate for making these concepts easy to understand 🙌 Excited to explore more and build strong fundamentals in Cloud & DevOps 🚀🔥 #CloudComputing #DevOps #Linux #LearningJourney

Most people fail at learning DevOps for one simple reason: They learn it in the wrong order. They jump into Docker, Kubernetes, and cloud tools… before they really understand Linux, networking, or Git. That’s why so many “DevOps roadmaps” look impressive but leave people lost. A path that makes more sense: Linux → Networking → Git → CI/CD → Docker → Kubernetes → Monitoring Simple. Logical. Practical. Because DevOps is not about collecting trendy tools. It’s about building the technical foundation that makes the rest useful. Learn the basics first. Then the advanced stack stops feeling complicated. That’s when real progress starts. What would you change in this roadmap? #DevOps #Linux #Kubernetes #Docker #CICD #Git #SysAdmin #SRE #Cloud #TechCareersq

🚀 𝐀𝐧𝐬𝐢𝐛𝐥𝐞 𝐁𝐞𝐬𝐭 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬 Most Ansible projects start simple… and slowly turn into something nobody understands 😵 👉 The fix isn’t more code 👉 The fix is structure Here’s what actually matters: ✔ Separate environments (dev / prod) ✔ Use roles — not giant playbooks ✔ No hardcoding — use variables ✔ Templates for dynamic configs ✔ Vault for secrets 🔐 ✔ Tags for control ✔ Always test before running 🎯 Result? ✔ Clean automation ✔ Reusable code ✔ Secure systems ✔ Scalable infrastructure 💬 Final thought The difference between: 👉 Ansible that works vs 👉 Ansible that scales 👉 Write once. Run forever. 🚀 #Ansible #DevOps #AWS #Automation #DevSecOps #Linux #Bash #TechLearning #DevOpsEngineer #CloudEngineering #CareerGrowth #CloudComputing #Tech #Cloud #LearningInPublic #LinkedInGrowth

🚀 Built a complete Infrastructure + Configuration Management setup using Terraform & Ansible Over the past few days, I worked on a hands-on project to automate provisioning and configuration of AWS infrastructure using Infrastructure as Code (IaC) and Configuration Management. Here’s what I implemented 👇 🔹 Terraform (Infra Layer) Provisioned EC2 instances (Ubuntu + Amazon Linux) Configured Security Groups (SSH + HTTP access) Managed SSH key pairs for secure access Structured code with reusable variables and provider configs 🔹 Ansible (Configuration Layer) Designed modular roles for: Nginx (supports both Ubuntu & Amazon Linux) Docker (Ubuntu-based setup) Implemented OS-based task execution using conditionals Used handlers for efficient service restarts Created multiple playbooks for real-world scenarios (setup, validation, loops, secrets) 🔹 Project Highlights Clean separation of infra (Terraform) and configuration (Ansible) Multi-environment inventory setup (dev & prod) Role-based architecture for scalability Secure handling of sensitive data using Ansible Vault End-to-end automation: from provisioning → configuration → deployment 📁 Structured repository with best practices: infra/ → Terraform code inventories/ → Environment-based inventories playbooks/ → Task execution roles/ → Reusable components 💡 This project helped me strengthen: Infrastructure automation Configuration management Writing reusable & scalable DevOps code Understanding cross-OS provisioning challenges Next steps: 🔐 Add HTTPS with Let's Encrypt 🐳 Extend Docker role with container deployments 🔁 Integrate CI/CD pipeline (GitHub Actions) Would love feedback or suggestions from the community! Repo : https://lnkd.in/gQHAtTgF #DevOps #Terraform #Ansible #AWS #InfrastructureAsCode #Automation #Cloud #LearningInPublic #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham

🚀 Day 4 of My Cloud & DevOps Bootcamp at Exlearn Technologies Today’s session with our mentor, Prashant Gavate, focused on one of the most essential skills for any aspiring Cloud & DevOps engineer — Linux 💻 🔍 Why Linux matters in Cloud & DevOps: • Most cloud platforms like AWS, Azure, and Google Cloud run on Linux-based systems • Offers better control, flexibility, and performance • Key DevOps tools like Docker, Kubernetes, and Jenkins are built around Linux • Powerful automation and scripting with Bash • Strong command-line skills are crucial for real-world server management 💡 Today, I explored Linux fundamentals, commands, file systems, and its role as the backbone of modern cloud infrastructure. This journey keeps getting more exciting as I move from theory to practical, real-world concepts. Looking forward to diving deeper into Linux and automation! 🔥 #Day4 #CloudComputing #DevOps #Linux #LearningJourney #ExlearnTechnologies #PrashantGavate #FutureEngineer

🚀 Most Engineers Get This Wrong in Ansible… Many engineers struggle with one simple thing: 👉 When to use an Ansible Playbook vs Ad-hoc Commands I was in the same place. After learning Ansible, I decided to go deeper and understand this clearly. 💡 In this post, I’ve explained: ✔ Why we use Ad-hoc Commands ✔ When to use them instead of playbooks ✔ How they help in real-time scenarios 🔥 My experience: When I executed my first Ansible ad-hoc command, it genuinely surprised me. From a single server, I was able to control multiple servers at once — run commands, create files, check systems… all in seconds. That moment made me realize how powerful automation can be. ⚡ Key takeaway: Not every task needs a playbook. Sometimes, a quick ad-hoc command is all you need. Ansible has been really interesting to learn, and this is just the beginning. 👉 In my next post, I’ll share how to write an Ansible Playbook step by step. Let’s keep learning and growing 🚀 #Ansible #DevOps #Automation #Linux #Cloud #LearningInPublic #DevOpsJourney #Fresher #Linux #DevOpsEngineer #DevOpsLife #DevOpsCommunity #CloudComputing #AWS #Azure #GCP #LinuxCommands #ShellScripting #Automation #CI_CD #Jenkins #Docker #Kubernetes #SRE #InfrastructureAsCode #PlatformEngineering #LearningInPublic #TechSkills #Engineering #ITCareers

📅Day 1 of my Terraform learning journey 🚀 Today I started learning Terraform and focused on understanding the basics along with setup and configuration on my Windows system. 🔹 What is Terraform? Terraform is an Infrastructure as Code (IaC) tool that allows us to create and manage cloud resources using code instead of doing everything manually from the console. 🔹 Why do we use it? ✔️ To automate infrastructure creation ✔️ To avoid manual errors ✔️ To maintain consistency across environments 🔹 Where is it useful in organizations? In real projects, multiple resources like servers, networks, and security configurations are required. Terraform helps teams manage all this using code, making deployment faster and more reliable. 🔹 What is Terraform State? Terraform state is used to keep track of the resources that Terraform creates. It helps Terraform understand what is already created and what changes are needed next time. 🔹 What I did today: ✔️ Installed Terraform on Windows ✔️ Configured AWS CLI for authentication ✔️ Understood basic Terraform workflow: init → plan → apply ✔️ Learned about Terraform state and why it is important 🔹 Advantages: ✔️ Saves time by automating tasks ✔️ Easy to track changes ✔️ Reusable code 🔹 Conclusion: Today’s learning gave me a clear idea of how infrastructure can be managed using code. It feels like a powerful approach, especially for working in real-time projects where consistency and automation are important. #Terraform #AWS #DevOps #Cloud

Day 4 of cloud and Devops bootcamp by Prashant Gavate and Exlearn Technologies we have gone through one important topic Linux OS and its importance. In today's cloud-native world, Linux isn't just a skill—it's the foundation powering 90%+ of cloud infrastructure (AWS, Azure, GCP) and DevOps tools like Kubernetes, Docker, Terraform, and Ansible. Why Linux matters in Cloud & DevOps: Containerization & Orchestration: Run Docker/K8s seamlessly on Linux kernels. Automation Mastery: Script with Bash/Python on servers where it counts. CI/CD Pipelines: Jenkins, GitLab CI thrive on Linux for reliability.