<?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 Afzal Ahmed on Medium]]></title>
        <description><![CDATA[Stories by Afzal Ahmed on Medium]]></description>
        <link>https://medium.com/@afzalahmed93?source=rss-e9f4cc5aeca5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Afzal Ahmed on Medium</title>
            <link>https://medium.com/@afzalahmed93?source=rss-e9f4cc5aeca5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:10:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@afzalahmed93/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[Week 2 at Cloud Engineer Academy]]></title>
            <link>https://medium.com/@afzalahmed93/week-2-at-cloud-engineer-academy-c43d1d339ef1?source=rss-e9f4cc5aeca5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c43d1d339ef1</guid>
            <category><![CDATA[cli]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Afzal Ahmed]]></dc:creator>
            <pubDate>Thu, 12 Feb 2026 11:35:35 GMT</pubDate>
            <atom:updated>2026-02-12T11:35:35.586Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Week 2 at Cloud Engineer Academy: Diving into Git, Cloud Architecture, and AWS CLI</strong></p><p>This week at Cloud Engineer Academy has been an intense and rewarding journey, covering everything from version control basics to designing a conceptual cloud architecture and hands-on AWS CLI experience. Here’s a recap of what I’ve learned and practiced.</p><p><strong>Getting Started with Version Control</strong></p><p>Understanding version control is foundational for any cloud or software engineering role. This week, I explored:</p><ul><li><strong>Git Basics:</strong> Learned what Git is and why it’s essential for tracking code changes.</li><li><strong>GitHub Introduction:</strong> Explored GitHub as a platform for hosting repositories and collaborating with teams.</li><li><strong>Creating a Repository &amp; Workflow:</strong> Learned how to create repositories, commit changes, and understand Git workflows.</li><li><strong>Access Keys vs Key Pairs:</strong> Clarified the differences between these authentication methods.</li><li><strong>Basic Git Commands:</strong> Practiced commands like git clone, git add, git commit, and git push.</li></ul><p><strong>Cloud Architecture Fundamentals</strong></p><p>I also delved into the principles of cloud architecture:</p><ul><li><strong>Evolution of Architecture &amp; System Design:</strong> Understood how modern architectures have evolved and the trade-offs involved.</li><li><strong>Front-End vs Back-End:</strong> Explored the responsibilities of each layer.</li><li><strong>Scaling:</strong> Learned the difference between vertical and horizontal scaling and when to apply each.</li><li><strong>Load Balancing, High Availability, and Fault Tolerance:</strong> Studied strategies for ensuring applications remain resilient under load.</li></ul><p><strong>Project One: Designing a Basic Cloud Architecture</strong></p><p>For my first project, I designed a conceptual architecture for a web application. Key steps included:</p><ul><li><strong>Identifying Core Components:</strong> Load balancer, frontend and backend servers, database, and storage.</li><li><strong>Determining Scaling Needs:</strong> Horizontal scaling for frontend and backend, vertical scaling with read replicas for the database.</li><li><strong>Conceptual Diagram:</strong> Created a traffic flow diagram from users → load balancer → servers → database → storage.</li><li><strong>Documenting Decisions:</strong> Considered high availability, redundancy, performance optimization, cost, and security.</li></ul><p><strong>Hands-On AWS CLI Experience</strong></p><p>I started hands-on practice with AWS CLI, focusing on S3 bucket management and IAM configuration. Key tasks completed:</p><ol><li>Installed and configured AWS CLI with IAM credentials.</li><li>Created S3 buckets and uploaded files.</li><li>Listed and downloaded files in buckets.</li><li>Created IAM users, attached policies, and generated access keys.</li><li>Used multiple CLI profiles for different environments.</li></ol><p>By the end of the week, I had completed the full S3 workflow:</p><ol><li>Create a bucket</li><li>Upload a file</li><li>List files in the bucket</li><li>Download a file</li></ol><p><strong>Summary of Skills Practiced</strong></p><p><strong>Version Control &amp; Git:</strong> Repository creation, workflows, and commands<br> <strong>Cloud Architecture:</strong> Designing scalable, secure, and highly available systems<br> <strong>AWS CLI &amp; S3:</strong> Bucket management, IAM configuration, and multi-profile CLI usage</p><p><strong>Reflections:</strong></p><p>Week 2 was all about bridging the gap between theory and practice. From learning Git basics to managing S3 buckets and designing a conceptual cloud architecture, I now feel more confident navigating the cloud ecosystem and understanding the architectural decisions behind modern web applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c43d1d339ef1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 1 at Cloud Engineer Academy — My First Steps into the Cloud]]></title>
            <link>https://medium.com/@afzalahmed93/week-1-at-cloud-engineer-academy-my-first-steps-into-the-cloud-a65a363ad13c?source=rss-e9f4cc5aeca5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a65a363ad13c</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Afzal Ahmed]]></dc:creator>
            <pubDate>Thu, 23 Oct 2025 12:08:20 GMT</pubDate>
            <atom:updated>2025-10-23T12:08:20.900Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 1 at Cloud Engineer Academy — My First Steps into the Cloud</h3><p><strong>Week 1 at Cloud Engineer Academy — My First Steps into the Cloud</strong></p><p>Starting my journey into cloud engineering has been both exciting and eye-opening. This week, I completed Week 1 of the Cloud Engineer Academy bootcamp, where we began exploring what the cloud really is, why it matters, and how to start working with it.</p><p><strong>Understanding Cloud Computing</strong></p><p>We kicked off with the fundamentals, what cloud computing actually means.<br> In simple terms, it’s the delivery of computing services such as servers, storage, databases, networking, and software over the internet (“the cloud”) instead of running them on your own physical hardware.</p><p>Some of the biggest benefits of cloud computing include:</p><ul><li>Scalability: Instantly adjust resources as your needs grow or shrink.</li><li>Cost efficiency: Only pay for what you use.</li><li>Accessibility: Work from anywhere with an internet connection.</li><li>Reliability: Take advantage of high availability and redundancy.</li></ul><p><strong>Cloud Deployment Models</strong></p><p>We explored the three main cloud deployment models — each offering different levels of control, flexibility, and cost.</p><ol><li>Public Cloud: Shared infrastructure managed by providers like AWS, Azure, or Google Cloud.</li><li>Private Cloud: Dedicated resources for a single organization.</li><li>Hybrid Cloud: A mix of both, providing flexibility and balance between security and scalability.</li></ol><p>Understanding when to use each model helps design the right infrastructure for different business needs.</p><p><strong>Setting Up My AWS Account</strong></p><p>To get hands-on, I created my AWS (Amazon Web Services) account and configured billing alerts. This step was essential. It’s the first real taste of working with cloud resources, and setting up billing properly helps avoid any unexpected costs while experimenting.</p><p><strong>Virtualization &amp; Networking Fundamentals</strong></p><p>Next, we dove into how virtualization underpins the cloud. I learned how one physical server can run multiple virtual machines, maximizing hardware efficiency and flexibility.</p><p>We also explored networking basics, focusing on how devices communicate across the internet and how IP addresses, routing, and DNS tie everything together.</p><p><strong>Hands-On Networking Practice</strong></p><p>Learning theory is one thing but, applying it is where things really click. Here’s what I practiced this week:</p><ul><li>Used curl on WSL to send a GET request and retrieve HTML from a web server.</li><li>Ran Tracert on Windows to trace the route packets take to a specific destination.</li><li>Found my local IP address using the Command Prompt.</li><li>Used ping to verify connectivity, one of the most basic yet powerful tools in network troubleshooting.</li></ul><p>Each exercise gave me a clearer picture of how data travels between systems and how the internet really works behind the scenes.</p><p><strong>Reflections on Week 1</strong></p><p>This week laid the foundation for my cloud journey. I now have a solid understanding of what the cloud is, why businesses rely on it, and how the underlying networking works.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a65a363ad13c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>