<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kachave Ashish on Medium]]></title>
        <description><![CDATA[Stories by Kachave Ashish on Medium]]></description>
        <link>https://medium.com/@kachaveashish281?source=rss-cb9160e75ead------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*M3fO-TNi8dNilq4xFJFrFw.png</url>
            <title>Stories by Kachave Ashish on Medium</title>
            <link>https://medium.com/@kachaveashish281?source=rss-cb9160e75ead------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:12:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kachaveashish281/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Infrastructure as Code (IaC) Explained with Terraform]]></title>
            <link>https://medium.com/@kachaveashish281/infrastructure-as-code-iac-explained-with-terraform-3e839023e779?source=rss-cb9160e75ead------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e839023e779</guid>
            <dc:creator><![CDATA[Kachave Ashish]]></dc:creator>
            <pubDate>Fri, 27 Mar 2026 05:38:29 GMT</pubDate>
            <atom:updated>2026-03-27T05:38:29.856Z</atom:updated>
            <content:encoded><![CDATA[<p>A few months ago, I was working late on a small cloud project. Nothing too serious, just something I wanted to try on my own. But I kept running into the same problem. I would set everything up, miss one tiny setting, and the whole thing would stop working. Then I’d go back, fix it, and somehow break something else.</p><p>After doing this a few times, I just sat there thinking, there has to be a better way to handle this.</p><p>That’s when I first heard about Infrastructure as Code. The idea sounded simple, but also a bit confusing. Instead of setting things up manually, you write down your infrastructure in a file and let a tool create it for you. It didn’t fully click at first, but I decided to try anyway.</p><p>I started using Terraform because it seemed beginner-friendly. My first attempt was very basic. I just wanted to create one server. I followed a small example, changed a few values, and ran it.</p><p>To my surprise, it worked on the first try.</p><p>I remember just staring at the screen for a few seconds. No clicking through menus, no guessing, no missed steps. Everything was created exactly the way I had written it.</p><p>A few days later, I needed to set up something similar again. Normally, that would mean repeating the same boring process. This time, I opened my file, changed a couple of lines, and ran it again. Done in minutes.</p><p>That’s when it really started to make sense.</p><p>What I liked most was how everything felt clear. Earlier, my setup existed only in my head or scattered across different screens. Now, it was all written in one place. If something went wrong, I could actually read through it and understand what I had done.</p><p>I even shared my configuration with a friend. Instead of explaining every step, I just sent him the file. He ran it and got the same setup. That moment made me realize how useful this approach really is, especially when working with others.</p><p>Of course, it wasn’t always smooth. There were times when things failed, and I had to figure out why. But even then, it felt different. I wasn’t randomly clicking around anymore. I was just adjusting my file and trying again.</p><p>Over time, this small change started affecting how I work. I stopped jumping straight into creating things and began thinking first. What exactly do I need? How should it be structured?</p><p>Now, whenever I start something new, I open a file before I open any cloud dashboard. It feels more organized, and honestly, less stressful.</p><p>Looking back, those frustrating moments were actually helpful. They pushed me to find a better way. And once I did, there was no going back.</p><p>Even today, whenever something feels repetitive, I pause for a second and ask myself if I can define it instead of doing it manually. Most of the time, the answer is yes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e839023e779" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Building Real Cloud Infrastructure on Microsoft Azure — My Week 8 DevOps Journey]]></title>
            <link>https://medium.com/@kachaveashish281/building-real-cloud-infrastructure-on-microsoft-azure-my-week-8-devops-journey-6c2dfb6c845f?source=rss-cb9160e75ead------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c2dfb6c845f</guid>
            <dc:creator><![CDATA[Kachave Ashish]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 10:40:40 GMT</pubDate>
            <atom:updated>2026-03-12T10:40:40.559Z</atom:updated>
            <content:encoded><![CDATA[<p>Cloud computing becomes truly meaningful when we move beyond theory and start building real infrastructure. During <strong>Week 8 of my DevOps Micro-Internship (DMI)</strong>, I had the opportunity to work hands-on with <strong>Microsoft Azure</strong>, implementing core cloud concepts through practical assignments.</p><p>This week focused on creating and managing real cloud infrastructure, deploying applications, and understanding how modern scalable systems are designed.</p><h3>☁️ Setting Up Azure Virtual Machines</h3><p>The first step was creating <strong>Azure Virtual Machines (VMs)</strong> to host applications.</p><p>I learned how to:</p><ul><li>Launch Linux VMs in Azure</li><li>Configure authentication using <strong>SSH keys</strong></li><li>Connect securely to the servers using SSH</li><li>Manage compute resources in the cloud</li></ul><p>This helped me understand how cloud providers deliver <strong>on-demand computing resources</strong> for applications.</p><h3>🌐 Designing Virtual Networks and Subnets</h3><p>Networking is a critical part of any cloud architecture.</p><p>I created a <strong>Virtual Network (VNet)</strong> and divided it into multiple <strong>subnets</strong> to separate different layers of the application.</p><p>The architecture included:</p><ul><li><strong>Web Tier Subnets (Public)</strong> — for frontend servers</li><li><strong>Application Tier Subnets (Private)</strong> — for backend services</li><li><strong>Database Tier Subnets (Private)</strong> — for secure database access</li></ul><p>This structure ensures <strong>network isolation and security</strong>, which is a key design principle in cloud environments.</p><h3>🔐 Secure Server Access Using SSH</h3><p>To manage cloud servers securely, I connected to the VMs using <strong>SSH</strong>.</p><p>This allowed me to:</p><ul><li>Access the Linux terminal remotely</li><li>Install required software packages</li><li>Configure servers for application deployment</li></ul><p>Learning SSH-based administration is an essential skill for <strong>DevOps engineers</strong>.</p><h3>⚙️ Installing and Configuring NGINX and Node.js</h3><p>Next, I installed and configured <strong>NGINX</strong> and <strong>Node.js</strong> on Azure VMs.</p><p>NGINX was used as a <strong>reverse proxy server</strong>, while Node.js hosted the backend application.</p><p>Responsibilities included:</p><ul><li>Installing NGINX on the server</li><li>Configuring reverse proxy rules</li><li>Running Node.js applications on specific ports</li><li>Managing application processes</li></ul><p>This setup reflects how real production systems handle <strong>web traffic routing and backend services</strong>.</p><h3>📦 Deploying Applications on Azure Virtual Machines</h3><p>After configuring the servers, I deployed the application onto the Azure VMs.</p><p>The deployment process involved:</p><ul><li>Uploading application code</li><li>Installing dependencies</li><li>Running services on cloud instances</li><li>Verifying application accessibility through public IP addresses</li></ul><p>This gave me practical experience with <strong>application deployment in the cloud</strong>.</p><h3>🔁 Configuring Azure Load Balancer</h3><p>To ensure high availability and traffic distribution, I configured an <strong>Azure Load Balancer</strong>.</p><p>Key tasks included:</p><ul><li>Creating a <strong>backend pool</strong></li><li>Setting up <strong>health probes</strong></li><li>Configuring <strong>load balancing rules</strong></li></ul><p>The load balancer distributes incoming requests across multiple servers, improving <strong>scalability and reliability</strong>.</p><h3>🏗️ Designing a Three-Tier Architecture</h3><p>One of the most important concepts I implemented was a <strong>Three-Tier Architecture</strong>.</p><p>The architecture included:</p><p><strong>1️⃣ Web Tier</strong></p><ul><li>Hosts the frontend application</li><li>Exposed to the internet through a public load balancer</li></ul><p><strong>2️⃣ Application Tier</strong></p><ul><li>Runs the backend services</li><li>Placed in private subnets for security</li></ul><p><strong>3️⃣ Database Tier</strong></p><ul><li>Stores application data</li><li>Accessible only from the application layer</li></ul><p>This design improves:</p><ul><li>Security</li><li>Scalability</li><li>Maintainability</li></ul><h3>📊 Key Learning Outcomes</h3><p>By the end of the week, I gained a deeper understanding of:</p><ul><li>Cloud infrastructure deployment</li><li>Virtual networking and subnet design</li><li>Load balancing and traffic management</li><li>Secure server configuration</li><li>Application deployment in a cloud environment</li><li>Real-world architecture patterns used in modern applications</li></ul><h3>💡 Final Thoughts</h3><p>Working directly on Azure helped me see how <strong>real-world cloud systems are built, deployed, and managed</strong>. Hands-on practice strengthened my understanding of networking, compute resources, and scalable application architecture.</p><p>This experience was an important step in my journey toward becoming a <strong>DevOps and Cloud Engineer</strong>.</p><p>I’m grateful for the opportunity to gain practical experience through the <strong>DevOps Micro-Internship program</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c2dfb6c845f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ My DevOps Journey: From Learning Agile & Jira to Deploying on AWS EC2]]></title>
            <link>https://medium.com/@kachaveashish281/my-devops-journey-from-learning-agile-jira-to-deploying-on-aws-ec2-4e286a43a6c0?source=rss-cb9160e75ead------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e286a43a6c0</guid>
            <dc:creator><![CDATA[Kachave Ashish]]></dc:creator>
            <pubDate>Fri, 06 Feb 2026 13:22:46 GMT</pubDate>
            <atom:updated>2026-02-06T13:22:46.385Z</atom:updated>
            <content:encoded><![CDATA[<h3>📌 DevOps Micro Internship (DMI) — Cohort 2</h3><p><strong>By Ashish Kachave</strong></p><p>DevOps is not just about tools — it is about collaboration, automation, and continuous delivery. During my <strong>DevOps Micro Internship (DMI) — Cohort 2</strong>, I gained hands-on experience working with <strong>Agile methodology, Jira project management, GitHub version control, and AWS deployment</strong>. This blog shares my learning journey and practical experience while building and shipping real project increments.</p><h3>🔍 Getting Started with Jira &amp; Agile Workflow</h3><p>Before this internship, I had very little exposure to Jira. However, through guided learning and hands-on tasks, I gradually became comfortable using it as a professional Agile project management tool.</p><h3>✅ What I Did</h3><ul><li>Created a Jira Cloud account and configured my professional profile</li><li>Explored Jira project navigation including:</li><li>Summary</li><li>Timeline</li><li>Backlog</li><li>Sprint Board</li><li>Reports</li><li>Understood how Agile teams organize and track development tasks</li></ul><h3>📘 What I Learned</h3><ul><li>Jira helps teams track work efficiently using Agile frameworks</li><li>Agile focuses on continuous improvement and iterative development</li><li>Proper project structure improves team collaboration and productivity</li></ul><h3>🧩 Setting Up Scrum Framework in Jira</h3><p>One of the key internship tasks was setting up Scrum for managing website development work.</p><h3>🎯 Creating Project, Epic, and Backlog</h3><p>I created a Jira project to manage development tasks for the DMI website improvement.</p><h4>✅ Tasks Completed</h4><ul><li>Created project: <strong>My_First_Project</strong></li><li>Created Epic: <strong>Polish DMI Website — UI &amp; Deploy</strong></li><li>Added multiple user stories such as:</li><li>Updating site header text</li><li>Improving UI button colors</li><li>Adding footer with deployment date</li><li>Adding contact and call-to-action sections</li><li>Assigned story points for effort estimation</li></ul><h4>📘 Learning Outcome</h4><ul><li>Epic represents large work goals</li><li>Stories break Epics into manageable tasks</li><li>Story points help estimate effort and sprint capacity</li></ul><h3>🔧 Breaking Stories into Subtasks</h3><p>To improve clarity and tracking, I divided stories into technical subtasks.</p><h3>✅ Example Workflow</h3><ul><li>Code modification (HTML / CSS / JavaScript)</li><li>Local testing</li><li>Deployment to EC2</li><li>Verification using live URL</li></ul><h3>📘 Key Learning</h3><p>Subtasks improve visibility and help teams track work step-by-step, which closely matches real DevOps workflows.</p><h3>🏷️ Using Labels &amp; Filters</h3><p>I learned how labels and filters help teams manage large projects.</p><h3>✅ Implementation</h3><ul><li>Tagged issues using labels like <strong>devops</strong>, <strong>frontend</strong>, etc.</li><li>Used filters to track assigned tasks and sprint progress</li></ul><h3>📘 Learning Outcome</h3><p>Filters improve productivity and help developers quickly focus on relevant tasks.</p><h3>⚡ Sprint Planning &amp; Execution</h3><p>I created and managed <strong>Sprint 1</strong> using Scrum principles.</p><h3>🎯 Sprint Goal</h3><p>Ship visible UI improvements and deploy updates to AWS EC2.</p><h3>✅ Activities Performed</h3><ul><li>Selected prioritized stories from backlog</li><li>Estimated tasks using story points</li><li>Started sprint execution</li><li>Tracked progress using Jira board</li></ul><h3>📘 What I Learned</h3><p>Sprint planning improves:</p><ul><li>Work prioritization</li><li>Delivery predictability</li><li>Team coordination</li></ul><h3>📊 Understanding Burnup Reports</h3><p>To monitor sprint progress, I used Jira burnup reports.</p><h3>✅ Report Insights</h3><ul><li>Compared planned work vs completed work</li><li>Monitored sprint progress visually</li><li>Identified scope changes</li></ul><h3>📘 Learning Outcome</h3><p>Burnup charts help teams evaluate performance and forecast delivery timelines.</p><h3>💻 Git &amp; GitHub Workflow Experience</h3><p>Version control is a core DevOps skill, and this internship helped me understand real collaborative workflows.</p><h3>✅ What I Practiced</h3><ul><li>Cloned repositories using HTTPS and SSH</li><li>Generated SSH keys</li><li>Created feature branches</li><li>Handled permission and authentication errors</li><li>Learned pull request workflows</li></ul><h3>📘 Learning Outcome</h3><p>I gained a clear understanding of distributed version control and collaborative development practices.</p><h3>🌐 Deploying Application on AWS EC2</h3><p>One of the most exciting parts of the internship was deploying the website live.</p><h3>✅ Deployment Steps</h3><ul><li>Launched AWS EC2 instance</li><li>Configured web server environment</li><li>Uploaded project files</li><li>Verified live website using public IP</li></ul><h3>📘 Learning Outcome</h3><p>This gave me practical exposure to:</p><ul><li>Cloud infrastructure setup</li><li>Application deployment lifecycle</li><li>Real-world DevOps delivery pipeline</li></ul><h3>🧠 Practical JavaScript Learning</h3><p>While improving UI components, I implemented dynamic functionality.</p><h3>✅ Example</h3><ul><li>Displayed live deployment date using JavaScript</li><li>Updated webpage dynamically using DOM manipulation</li></ul><h3>📘 Learning Outcome</h3><p>I learned how dynamic UI improves user experience and reduces manual updates.</p><h3>🔄 Sprint Retrospective Experience</h3><p>I documented sprint retrospective notes focusing on:</p><ul><li>What went well</li><li>Improvement areas</li><li>Scrum values and pillars</li></ul><p>This helped me understand how Agile teams continuously improve delivery processes.</p><h3>⭐ Key Skills I Developed</h3><p>✔ Agile &amp; Scrum Methodology<br> ✔ Jira Project &amp; Sprint Management<br> ✔ Git &amp; GitHub Collaboration<br> ✔ AWS EC2 Deployment<br> ✔ Frontend UI Enhancement<br> ✔ DevOps Workflow Understanding</p><h3>🎯 Final Thoughts</h3><p>This internship transformed my understanding of DevOps from theoretical knowledge to real-world application. I learned how development, testing, deployment, and monitoring work together in a continuous delivery pipeline.</p><p>Most importantly, I understood that DevOps is not just about tools — it is about collaboration, transparency, and continuous improvement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e286a43a6c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Local Commits to Pull Requests: My Week 3 DevOps Journey with Git & GitHub ]]></title>
            <link>https://medium.com/@kachaveashish281/from-local-commits-to-pull-requests-my-week-3-devops-journey-with-git-github-f654add3428a?source=rss-cb9160e75ead------2</link>
            <guid isPermaLink="false">https://medium.com/p/f654add3428a</guid>
            <dc:creator><![CDATA[Kachave Ashish]]></dc:creator>
            <pubDate>Fri, 30 Jan 2026 05:51:22 GMT</pubDate>
            <atom:updated>2026-01-30T05:51:22.481Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>DevOps Micro Internship (DMI) — Cohort 2 | Week 3</strong></p><p>In DevOps, tools matter — but <strong>workflows matter more</strong>.<br> Week 3 of the DevOps Micro Internship (DMI) was a deep, hands-on dive into <strong>Git, GitHub, and real-world collaboration practices</strong>. This wasn’t about memorizing commands; it was about understanding how modern teams build, track, and ship software together.</p><p>This blog documents what I built, what I broke, and — most importantly — what I learned.</p><h3>🔧 Assignment 1: Git Setup &amp; Identity — Local vs Global</h3><p>I began by creating a project called <strong>CodeTrack</strong> and initializing it as a Git repository.</p><h3>What I did</h3><ul><li>Initialized a Git repository using git init</li><li>Configured <strong>local Git identity</strong> (repo-specific)</li><li>Verified <strong>global Git identity</strong> (machine-wide)</li></ul><h3>Key takeaway</h3><blockquote><em>Git identity isn’t just configuration — it’s </em><strong><em>accountability</em></strong><em>.</em></blockquote><ul><li>Local config is preferred in enterprise environments</li><li>Global config acts as a fallback</li><li>Local settings always override global ones</li></ul><p>This helped me understand how Git tracks <em>who</em> made <em>which</em> change — and <em>where</em> that identity applies.</p><h3>📦 Assignment 2: Tracking, Staging, Committing &amp; Deploying to EC2</h3><p>This assignment simulated a real development lifecycle — from code creation to deployment.</p><h3>What I built</h3><ul><li>Created index.html and style.css</li><li>Added real HTML/CSS content</li><li>Practiced clean staging with git add</li><li>Wrote <strong>meaningful, scoped commits</strong></li><li>Deployed the static site to <strong>AWS EC2 using Nginx</strong></li></ul><h3>What I learned</h3><ul><li>git status is your best debugging partner</li><li>Staging allows <strong>intentional commits</strong></li><li>Small, focused commits make history readable</li><li>Deployment is just another step in the workflow — not magic</li></ul><p>Seeing my project live via an <strong>EC2 public IP</strong> made the learning tangible. Code finally met reality.</p><h3>🌿 Assignment 3: Branching Workflow — Feature Development Done Right</h3><p>This was my first proper experience working with <strong>feature branches</strong>.</p><h3>Workflow I followed</h3><ul><li>Confirmed a clean default branch</li><li>Created feature/contact-page</li><li>Added contact.html</li><li>Updated navigation in index.html</li><li>Verified isolation from the main branch</li><li>Merged safely back into main</li><li>Inspected commit history using git log --graph</li><li>Cleaned up the feature branch</li></ul><h3>Big lesson</h3><blockquote><em>Feature branches protect stability.</em></blockquote><p>They allow experimentation without risking the main codebase — this is how teams move fast <strong>without breaking production</strong>.</p><h3>🌐 Assignment 4: GitHub Setup &amp; Professional Presence</h3><p>GitHub isn’t just a code host — it’s a <strong>portfolio</strong>.</p><h3>What I did</h3><ul><li>Reviewed and optimized my GitHub profile</li><li>Explored trending repositories</li><li>Starred and forked open-source projects</li><li>Understood the difference between <strong>starring vs forking</strong></li></ul><h3>Insight</h3><p>A clean GitHub profile tells your learning story <strong>before you ever speak to a recruiter</strong>.</p><h3>🤝 Assignment 5: Hands-on GitHub Collaboration (My First Pull Request)</h3><p>This was the highlight of the week.</p><h3>The Open Source Workflow I followed</h3><ul><li>Forked the upstream repository</li><li>Cloned my fork locally</li><li>Set up two remotes:</li><li>origin → my fork</li><li>upstream → original repo</li><li>Created a feature branch</li><li>Pushed changes to my fork</li><li>Opened a <strong>Pull Request</strong></li></ul><h3>The mindset shift</h3><blockquote><em>A Pull Request is not a file transfer — it’s a </em><strong><em>conversation</em></strong><em>.</em></blockquote><p>This taught me how distributed teams collaborate without stepping on each other’s work.</p><h3>📌 What This Week Really Taught Me</h3><ul><li>Practice beats theory — every time</li><li>Clean commits matter</li><li>Branching enables safe collaboration</li><li>Deployment closes the feedback loop</li><li>DevOps is as much about <strong>communication</strong> as it is about tools</li></ul><h3>🔗 Links &amp; Proof of Work</h3><ul><li>GitHub Profile:<br> <a href="https://github.com/ashish-kachave">https://github.com/ashish-kachave</a> <em>(if you want, add this)</em></li><li>LinkedIn Post (Week 3):<br> <a href="https://www.linkedin.com/posts/ashish-kachave-28462a389_this-week-was-all-about-hands-on-learning-activity-7422877181858656257-PpM6">https://www.linkedin.com/posts/ashish-kachave-28462a389_this-week-was-all-about-hands-on-learning-activity-7422877181858656257-PpM6</a></li></ul><h3>🙌 Final Thoughts</h3><p>Week 3 wasn’t easy — but it was <strong>real</strong>.<br> I didn’t just learn Git commands; I learned how <strong>real teams think, work, and collaborate</strong>.</p><p>Grateful to the <strong>DevOps Micro Internship (DMI)</strong> and mentors for designing learning that mirrors industry reality.</p><p>Onward to the next challenge 🚀</p><h3>✍️ Author</h3><p><strong>Ashish Kachave</strong><br> DevOps Learner | Cloud &amp; GitHub Enthusiast<br> 📍 India</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f654add3428a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a React App on AWS EC2 with Nginx: My Week 2 DevOps Journey]]></title>
            <link>https://medium.com/@kachaveashish281/deploying-a-react-app-on-aws-ec2-with-nginx-my-week-2-devops-journey-a40a7ecc57ea?source=rss-cb9160e75ead------2</link>
            <guid isPermaLink="false">https://medium.com/p/a40a7ecc57ea</guid>
            <dc:creator><![CDATA[Kachave Ashish]]></dc:creator>
            <pubDate>Fri, 23 Jan 2026 10:50:39 GMT</pubDate>
            <atom:updated>2026-01-23T10:50:39.373Z</atom:updated>
            <content:encoded><![CDATA[<p>Deploying a React App on AWS EC2 with Nginx: My Week 2 DevOps Journey</p><p>As part of the DevOps Micro Internship (DMI) Cohort 2, I spent Week 2 diving deeper into Linux, AWS, and web server deployment. This week was all about hands-on learning, moving beyond tutorials and really understanding how applications are deployed and served in real-world environments.</p><p>One of the highlights of the week was deploying my React application on an AWS EC2 instance using Nginx. This was not just a task — it was an experience that taught me how web servers work, how content is served, and how deployment pipelines can be streamlined.</p><p>Setting the Stage: Linux and AWS Basics</p><p>Before deploying, I focused on building a solid foundation:</p><p>Navigating the Linux terminal confidently</p><p>Understanding file permissions and processes</p><p>Monitoring system performance</p><p>Learning essential Linux commands for deployment</p><p>These skills proved invaluable when configuring the EC2 instance and setting up the server environment.</p><p>Deployment Process</p><p>Here’s a high-level overview of what I did:</p><p>Created an AWS Free Tier EC2 instance and connected via SSH using MobaXterm.</p><p>Installed and configured Nginx to serve as the web server.</p><p>Cloned my React app repository into /var/www/html.</p><p>Updated the index.html and other static assets to ensure the website displayed correctly.</p><p>Verified the server was running, and finally, the website went live!</p><p>🌐 Check it out here: <a href="http://100.27.250.149/">http://100.27.250.149/</a></p><p>Key Learnings</p><p>This deployment taught me several valuable lessons:</p><p>Reusability over redundancy: Instead of launching a new server for minor changes, I reused the same EC2 instance efficiently.</p><p>Nginx configuration: I learned how to configure Nginx to serve static content and manage multiple sites if needed.</p><p>Hands-on server management: SSH-based workflows gave me confidence in managing Linux servers without relying solely on web consoles.</p><p>AWS experience: Gained practical knowledge of EC2 instances and cloud deployment.</p><p>Final Thoughts</p><p>Deploying a React app on AWS EC2 using Nginx might seem daunting at first, but breaking the process into small steps made it manageable and extremely rewarding. Week 2 of DMI reinforced that hands-on practice is the fastest way to learn DevOps.</p><p>I’m grateful to Pravin Mishra and our mentors for their structured guidance, and I look forward to continuing this journey, learning more about cloud infrastructure, Linux administration, and real-world deployment workflows.</p><p>#DevOps #AWS #EC2 #Nginx #ReactJS #Linux #CloudComputing #LearningByDoing #DMIByPravinMishra</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a40a7ecc57ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Stopped Chasing Marks and Started Building Skills]]></title>
            <link>https://medium.com/@kachaveashish281/why-i-stopped-chasing-marks-and-started-building-skills-f526b1bf4874?source=rss-cb9160e75ead------2</link>
            <guid isPermaLink="false">https://medium.com/p/f526b1bf4874</guid>
            <dc:creator><![CDATA[Kachave Ashish]]></dc:creator>
            <pubDate>Fri, 16 Jan 2026 11:10:06 GMT</pubDate>
            <atom:updated>2026-01-16T11:10:06.042Z</atom:updated>
            <content:encoded><![CDATA[<p>For a long time, I believed what most students around me believed — that marks, ranks, and degrees decide our future. But slowly, through my own experiences, I realized something different:</p><p><strong>Academic success is important, but continuous self-learning and practical skills are far more powerful.</strong></p><p>Today, I want to share how this mindset changed my direction, discipline, and career vision.</p><h3>The Three Truths I Learned From Experience</h3><h3>1. Consistency Beats Last-Minute Effort</h3><p>When I studied daily for one subject, my understanding became deeper and my confidence improved. When I studied only before exams, I felt stressed and confused. Regular effort gave me stability and clarity.</p><h3>2. Practical Learning Works Faster Than Theory</h3><p>Reading books helped, but applying concepts in projects helped much more. My mistakes taught me more than any page in a notebook ever could.</p><h3>3. Discipline Is Stronger Than Motivation</h3><p>Motivation is temporary. Discipline is permanent. On days I waited for motivation, I wasted time. On days I followed a routine, I progressed.</p><h3>My DevOps 2.0 Vision</h3><p>I imagine my future self as a DevOps professional who builds systems, not just certificates.</p><p>By 2029, I see myself working as a DevOps Engineer who:</p><ul><li>Automates deployments using CI/CD pipelines</li><li>Works with Docker, Kubernetes, Terraform, and cloud platforms</li><li>Builds reliable monitoring systems</li><li>Documents learning openly to help beginners</li><li>Contributes to open-source projects</li><li>Mentors juniors with patience and honesty</li></ul><p>My journey started seriously when I joined the <strong>DevOps Micro Internship (DMI) by Pravin Mishra</strong>. This program taught me that learning is not about memorizing tools — it is about applying, documenting, and improving continuously.</p><h3>A Lesson From Taking Shortcuts</h3><p>Yes, I have cut corners before.</p><p>And every time, I felt guilt, discomfort, and fear. Even if the result looked fine, inside I knew I didn’t truly earn it. That feeling reduced my confidence instead of increasing it.</p><p>Shortcuts saved time temporarily, but they created long-term stress and self-doubt.</p><p>That experience taught me to respect honest effort.</p><h3>The System I Now Follow</h3><p>Instead of depending on motivation, I now depend on systems:</p><ul><li>60 minutes daily DevOps deep work</li><li>Phone on silent during focus time</li><li>Weekly review and planning</li><li>One task at a time</li><li>Clean workspace, clear mind</li></ul><p>This simple system is slowly changing my habits, mindset, and future.</p><h3>What I Measure Now</h3><p>I no longer measure only marks.<br> I measure:</p><ul><li>Learning hours</li><li>Screen time</li><li>Focus sessions</li><li>Habit consistency</li><li>Financial awareness</li></ul><p>Because <strong>what we measure, we improve.</strong></p><h3>Final Thought</h3><p>I am not extraordinary.<br> I am not perfect.<br> I am still learning.</p><p>But I am consistent.</p><p>And today, I believe this deeply:</p><blockquote><em>Certificates may open doors, but skills decide how long you stay inside.</em></blockquote><p>My journey in DevOps is just beginning — but now it has direction, discipline, and purpose.</p><h3>About Me</h3><p>I am Ashish Kachave, a Computer Science graduate and DevOps learner building my career through structured systems, real projects, and continuous self-improvement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f526b1bf4874" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>