<?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 Iris Damani on Medium]]></title>
        <description><![CDATA[Stories by Iris Damani on Medium]]></description>
        <link>https://medium.com/@irisdamani?source=rss-cd4007fa096------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DqPa-rS89hw_39obJ28DlA.jpeg</url>
            <title>Stories by Iris Damani on Medium</title>
            <link>https://medium.com/@irisdamani?source=rss-cd4007fa096------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:34:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@irisdamani/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: Designing My First AWS Infrastructure]]></title>
            <link>https://medium.com/@irisdamani/week-2-designing-my-first-aws-infrastructure-fbeb3203a0d4?source=rss-cd4007fa096------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbeb3203a0d4</guid>
            <dc:creator><![CDATA[Iris Damani]]></dc:creator>
            <pubDate>Thu, 30 Oct 2025 14:17:19 GMT</pubDate>
            <atom:updated>2025-11-06T13:02:54.823Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Journey from Code to Management… and Back Again</h3><p>I spent years doing what I loved: writing Node.js backends, <strong>designing scalable APIs</strong>, building systems that worked. Then I became a Technical Project Manager. On paper, it looked like career progression. Better title, more responsibility, leading teams through cloud infrastructure projects.</p><p>But something felt wrong.</p><p>I’d sit in architecture review meetings, nodding along as my team debated VPC configurations, subnet strategies, and load balancer types. I’d review AWS cost reports without fully understanding what we were paying for. I was <em>managing</em> cloud infrastructure projects, but I wasn’t <em>building</em> anymore. I was watching others do the technical work I desperately missed.</p><p>That realization hit hard: <strong>I didn’t want to manage engineers. I wanted to BE the engineer again but this time, in the cloud.</strong></p><h3>Starting Over: Week 2 of My Cloud Engineering Journey</h3><p>Two weeks ago, I enrolled in Soleyman’s Cloud Engineering Academy with one clear goal: transition from Technical Project Manager to Cloud Architect/Engineer. Not because management is bad, but because my heart is in building, designing, and solving technical problems.</p><p>Now I’m in Week 2, and I’ve decided to document everything. Not just for myself, but for anyone else who’s ever felt that pull back to technical work. This is my journey of building the skills to design, implement, and manage cloud infrastructure at scale.</p><p>This week’s challenge? <strong>Design a complete web application infrastructure on AWS from scratch. A basic one but at least smth that can be scale latter.</strong></p><p>Let me walk you through what I learned, what surprised me, and why this week felt like coming home.</p><h3>The Assignment: Build a Production-Ready AWS Infrastructure</h3><p>The goal was clear: design a scalable, highly available infrastructure for a simple web application. Coming from a backend development background, I thought, “How hard could this be? I’ve built Node.js APIs before.”</p><p><strong>I was humbling wrong.</strong></p><p>Building a single-server backend is one thing. Designing cloud infrastructure that can handle failures, scale automatically, and stay secure? That’s an entirely different beast.</p><p>Here’s what I had to figure out:</p><ul><li>How do users reach my application reliably?</li><li>What happens when a server fails?</li><li>How do I separate frontend, backend, and database securely?</li><li>Where do I store files? How do I handle traffic spikes?</li><li>How do I ensure my data isn’t lost?</li></ul><p>Let me show you the architecture I designed and the lessons I learned along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m9LFB5YCBgAh7jqZid_qLA.png" /><figcaption>AWS Basic Architecture</figcaption></figure><p>System Flow Overview</p><p>User Request:The user initiates a request to the e-commerce website to view recent products.</p><p>DNS Resolution (Route 53): The request is first routed through Amazon Route 53, which functions as a DNS service. Route 53 checks the health of the application resources to ensure that all services are reachable and operational before forwarding the request.</p><p>Content Delivery (CloudFront):Once validated, the request is directed to Amazon CloudFront, which delivers and hosts the frontend (FE) application for improved performance and lower latency.</p><p>Frontend Interaction: User interactions on the frontend trigger API calls to the backend services for data retrieval or other operations.</p><p>Load Balancing: A load balancer is recommended at this stage to distribute incoming traffic evenly across multiple backend instances, ensuring high availability and scalability.</p><p>Backend Processing: The backend receives the request, processes it, and retrieves the necessary data either from a database or an Amazon S3 bucket, depending on the type of resource requested.</p><p>Response Delivery: The backend sends the processed response back and the requested content is displayed to the user on the frontend.</p><p>To support the flow i decide to use those compontents:<br><strong>Elastic Compute Cloud (EC2)</strong>: Virtual servers running your <strong>frontend</strong> and <strong>backend</strong> applications. Those instances are grouped in <strong>Auto Scaling Groups</strong> to automatically adjust capacity based on traffic or performance.</p><p><strong>Elastic Load Balancer (ELB):</strong>Distributes incoming traffic (API requests) evenly across multiple EC2 instances in the backend ASG. Improves availability and reliability by preventing any single instance from becoming overloaded.</p><p><strong>Amazon RDS (Relational Database Service): </strong>A managed relational database service that stores structured data such as user accounts, transactions, or product information.Provides automatic backups, scalability, and high availability.</p><p><strong>Amazon S3 (Simple Storage Service):</strong>Object storage service used for hosting static assets such as images, documents, or other media files.The backend retrieves or stores files here as needed.</p><h3>How this application will scale ?</h3><p>Scalability ensures that the application can handle increasing (or decreasing) levels of traffic and workload efficiently without impacting performance or availability.<br> Architecture that i proposed supports both <strong>horizontal</strong> and <strong>vertical</strong> scaling strategies, primarily through <strong>Auto Scaling</strong>, <strong>Load Balancing</strong>, and <strong>managed AWS services</strong>. So, Frontend and Backend EC2 Instances will be configured to support horizontal scaling, automatically <strong>adds new EC2 instances</strong> when traffic increases (scale out) and <strong>terminates instances</strong> when demand decreases (scale in). <strong>Elastic Load Balancer (ELB),</strong>dynamically distributes incoming traffic across all healthy EC2 instances which eliminates single points of failure and supports <strong>horizontal</strong> scalability. <strong>RDS</strong> supports both vertical and horizontal scaling and <strong>S3</strong> bucket automatically scales to handle virtually unlimited amounts of data and concurrent access.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbeb3203a0d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>