<?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 Oyame Ogbeche on Medium]]></title>
        <description><![CDATA[Stories by Oyame Ogbeche on Medium]]></description>
        <link>https://medium.com/@oyogbeche?source=rss-f628a267b4db------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Tv2spThZYdDcZv3mIBR9Xw.jpeg</url>
            <title>Stories by Oyame Ogbeche on Medium</title>
            <link>https://medium.com/@oyogbeche?source=rss-f628a267b4db------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:54:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oyogbeche/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[Building a Lightweight Container from Scratch: A Simple Guide]]></title>
            <link>https://medium.com/@oyogbeche/building-a-lightweight-container-from-scratch-a-simple-guide-90885eeb2d10?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/90885eeb2d10</guid>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Fri, 28 Mar 2025 22:57:10 GMT</pubDate>
            <atom:updated>2025-03-30T09:32:08.423Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Imagine you live in a house with roommates who love borrowing your stuff without asking. Annoying, right? Now, imagine you build yourself a mini-house <em>inside</em> the house, with separate locks, a private kitchen, and a soundproof wall. Your roommates can do whatever they want, but they can’t touch your things. That’s exactly what containerization does for applications!</p><p>While Docker makes this process super easy, today, we’re going “Old-school” by building an isolated application environment manually using Linux namespaces, cgroups, and chroot. Think of it as making a homemade burger instead of buying one from KFC, it’s more effort, but you really understand what goes inside!</p><p>By the end of this, we’ll have our own mini-container running an application, completely separate from the host system.</p><h3>Step 1: Setting Up an Isolated Environment</h3><p>Let’s create our Isolated env, for simplicity we will call it “isolated-env”</p><pre>mkdir -p /opt/isolated-env</pre><h3>Process Isolation with Namespaces</h3><p>Linux namespaces are like VIP sections in a club — only certain people (processes) can access them.</p><h4>Create a new PID namespace</h4><p>A new PID namespace ensures that processes inside our environment don’t interfere with the host.</p><pre>unshare --fork --pid --mount-proc bash</pre><p>By running the command:</p><pre>ps aux</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*aDYD9UXQDmUyBxYBZWX4zQ.png" /></figure><p>It only shows processes inside your namespace. This confirms the PID isolation.</p><h4>Isolate Users with a User Namespace</h4><pre>unshare --user --map-root-user --mount bash</pre><p>This maps the root user inside the environment to a non-root user on the host. So, whatever happens in the isolated environment, it can’t mess with the host system!</p><p><strong>Note:</strong> unshare is not very persistent and dies when the shell exist.</p><p>For a more persistent Namespace Isolation you can mount and attach it</p><pre>sudo mkdir -p /var/run/isolated-env<br>sudo touch /var/run/isolated-env/pidns<br>sudo touch /var/run/isolated-env/userns<br><br>unshare --fork --pid --user --map-root-user --mount-proc bash<br><br><br>mount --bind /proc/$$/ns/pid /var/run/isolated-env/pidns<br>mount --bind /proc/$$/ns/user /var/run/isolated-env/userns</pre><p>you can alway re-enter the namespace with</p><pre>nsenter --pid=/var/run/isolated-env/pidns --user=/var/run/isolated-env/userns bash</pre><p>This way, the PID and user namespaces persist, allowing you to reconnect after closing the session.</p><h4><strong>For Network Isolation: Where you get your own network playground</strong></h4><p>First you need to create a dedicated network namespace for your isolated env, we will call it: ‘mynet’</p><pre>ip netns add mynet<br>ip netns exec mynet bash</pre><p>This creates a loopback network interface which allows process in the network namespace to communicate with each other but still isolated from the host network and by default it is usually DOWN and you have to bring it UP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*2mb80HSkBkxN0Q0Juwv8ig.png" /><figcaption>You can clearly observe I can’t ping google.com from the isolated environment</figcaption></figure><p>To be able to access external network you will need to create a virtual network interface and add an private IP CIDR block to it.</p><pre>sudo ip link add veth0 type veth peer name veth1<br><br>sudo ip link set veth1 netns mynet<br><br>sudo ip addr add 192.168.1.1/24 dev veth0<br>sudo ip netns exec mynet ip link set veth1 up<br><br>sudo ip netns exec mynet ip addr add 192.168.1.2/24 dev veth1<br>sudo ip link set veth0 up<br><br>sudo ip netns exec mynet ip link set veth1 up<br></pre><p>Setting up NAT and routing</p><pre>sudo sysctl -w net.ipv4.ip_forward=1<br>sudo bash -c &#39;echo &quot;net.ipv4.ip_forward=1&quot; &gt;&gt; /etc/sysctl.conf&#39;<br>sudo cp /etc/resolv.conf /opt/isolated-env/etc/resolv.conf<br><br>ip netns exec mynet ip route add default via 192.168.1.1<br><br>sudo iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -j MASQUERADE</pre><p>after adding the external network interface we can now successfully connect to the internet from the isolated environment.</p><p>we can enter back into the isolated env, this time also specifying the network namespace for the isolated env.</p><pre>nsenter --pid=/var/run/isolated-env/pidns --user=/var/run/isolated-env/userns --net=/var/run/netns/mynet bash</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*23NO5tZu5a4gMFFjHtmrPw.png" /><figcaption>we can now ping google.com and packets are sent and received as well.</figcaption></figure><h3>Step 2: Filesystem Isolation with Chroot</h3><p>Imagine you’re moving into a new apartment. You need your furniture, but not your annoying neighbors. We need to create a separate root filesystem for our application.</p><h3>Create a Minimal Root Filesystem</h3><pre>sudo mkdir -p /opt/isolated-env/{bin,lib64,dev,proc,sys,tmp}</pre><p>Let’s copy over essential system files</p><pre>sudo cp /bin/bash /opt/isolated-env/bin/<br>sudo cp /bin/ls /opt/isolated-env/bin/<br>sudo cp /bin/sh /opt/isolated-env/bin/</pre><p>and the neccessary shared libaries</p><pre>sudo ldd /bin/bash /bin/ls | awk &#39;{print $3}&#39; | grep -v &#39;^$&#39; | xargs -I {} cp {} /opt/isolated-env/lib64/</pre><h3>Step 3: Controlling Resource Usage with Cgroups</h3><p>Let’s make sure our container doesn’t eat up all the system’s CPU, memory and Disk (like that one friend who always finishes the snacks).</p><h3>3.1 Set Up a New Cgroup</h3><p>Create a new cgroup directory for the isolated environment</p><pre>mkdir -p /sys/fs/cgroup/isolated-env</pre><p>then enable CPU, Memory and Disk limits</p><pre>echo &quot;+cpu +memory +io&quot; &gt; /sys/fs/cgroup/isolated-env/cgroup.subtree_control</pre><p>Limit CPU usage</p><pre>echo 100000 &gt; /sys/fs/cgroup/isolated-env/cpu.max</pre><p>Limit Memory usage</p><pre>echo 500M &gt; /sys/fs/cgroup/isolated-env/memory.max</pre><p>Limi]t Disk usage</p><pre>echo &quot;202:0 rbps=10485760 wbps=5242880&quot; &gt; /sys/fs/cgroup/isolated-env/io.max</pre><h3><strong>Step 4: System Call Limitation with AppArmor</strong></h3><p>AppArmor is a Mandatory Access Control (MAC) system that provides an additional layer of security by confining programs to a limited set of resources and preventing unauthorized actions.</p><p>Create an AppArmor Profile: /etc/apparmor.d/isolated-env</p><pre>sudo tee /etc/apparmor.d/isolated-env &lt;&lt;EOF<br>#include &lt;tunables/global&gt;<br><br>/opt/isolated-env/** {<br>  deny mount,<br>  deny ptrace,<br>  deny setuid,<br>  deny setgid,<br>  deny exec /usr/bin/sudo,<br>  deny exec /bin/su,<br>}<br>EOF</pre><p>Load the profile</p><pre>sudo apparmor_parser -r /etc/apparmor.d/isolated-env</pre><h3><strong>Step 5: Change Root to the Isolated Environment</strong></h3><pre>chroot /opt/isolated-env /bin/bash</pre><p>This allows your isolated-env to become it’s own root. Welcome to your new home. Just like some people describe Docker as Chroot on steriods.</p><h3>Step 6: Running an Application Inside the Environment</h3><p>let’s run an application inside our isolated environment, We would run a simple python fast api application.</p><p>Install dependencies and start the application</p><pre>from fastapi import FastAPI<br>import os<br>import socket<br>import platform<br><br>app = FastAPI()<br><br>@app.get(&quot;/&quot;)<br>def read_root():<br>    return {&quot;message&quot;: &quot;Hello from isolated environment&quot;}<br><br>@app.get(&quot;/system-info&quot;)<br>def system_info():<br>    return {<br>        &quot;hostname&quot;: socket.gethostname(),<br>        &quot;os_release&quot;: platform.release(),<br>        &quot;process_id&quot;: os.getpid(),<br>        &quot;parent_process_id&quot;: os.getppid(),<br>        &quot;current_directory&quot;: os.getcwd(),<br>        &quot;root_directory_contents&quot;: os.listdir(&quot;/&quot;),<br>    }</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*sXKPeLnXFuRC9tixUsQnVQ.png" /></figure><h3>Conclusion</h3><p>We built our own <strong>lightweight container</strong> from scratch, just like a homemade burger. This is what tools like Docker do under the hood but with way more automation. Now, if someone asks, “What even <em>is</em> containerization?”, you can just say: <em>“It’s like moving into a house with separate locks and WiFi. You’re in the same building, but no one can touch your stuff!”</em></p><p>Feel free to twitch this as much as possible to fit your use case.</p><p>Next time, we’ll automate this process using a script so you won’t have to type everything manually. Stay tuned and enjoy your new home.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90885eeb2d10" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real World Project: Building a Containerized Sports API with AWS]]></title>
            <link>https://medium.com/@oyogbeche/real-world-project-building-a-containerized-sports-api-with-aws-a6d05c5b6cb3?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6d05c5b6cb3</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[nfl]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 03:10:35 GMT</pubDate>
            <atom:updated>2025-01-27T03:10:35.925Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Introduction</strong></h4><p>What do the NFL and DevOps have in common? Both require seamless coordination and execution to win. I recently completed a project that blended football with my passion for cloud architecture — a <strong>containerized sports API</strong> for NFL game schedules. This project not only served fans with real-time schedules but also featured a CI/CD pipeline, ensuring that updates roll out as smoothly as a Tom Brady touchdown pass.</p><p>Let me walk you through the playbook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xCubNZ7epZFDvJV7JGv74A.jpeg" /></figure><h4>Project Breakdown: The Game Plan</h4><h4>The Backfield (Backend) Setup</h4><p>At the core of this project is a <strong>containerized sports API</strong> powered by SERPAPI to fetch NFL game schedules. The backend is built to be highly scalable and reliable. Here’s how the play unfolded:</p><ul><li><strong>ECS (Elastic Container Service)</strong>: Used to deploy and manage the containerized sports API. ECS acted like my offensive line, protecting and running the API with efficiency.</li><li><strong>ECR (Elastic Container Registry)</strong>: Stored Docker images securely, ensuring that every deployment pulled the latest, optimized image.</li><li><strong>Application Load Balancer (ALB)</strong>: Routed traffic seamlessly to ensure that API users always had a smooth experience — no fumbles allowed.</li><li><strong>API Gateway</strong>: Provided an additional layer of control, enabling rate limiting and fine-tuning how requests were handled.</li><li><strong>Auth0</strong>: Secured the API with robust authorization, ensuring only verified users could access the endpoints</li></ul><h4>CI/CD Pipeline: Automating the Plays</h4><p>No successful team skips practice, and in the DevOps world, that means CI/CD. I set up a <strong>GitHub Actions pipeline</strong> to automate the process:</p><ol><li><strong>Code Push</strong>: Whenever new code is pushed to the repository, GitHub Actions triggers a workflow.</li><li><strong>Build Docker Image</strong>: The workflow builds the API’s Docker image and tags it with the latest version.</li><li><strong>Push to ECR</strong>: The image is then pushed to <strong>AWS ECR</strong>, ready for deployment.</li></ol><p><em>Key Benefits</em>: This CI/CD setup ensures every update is automated, consistent, and error-free.</p><h4>The Frontline: A User-Friendly Web UI</h4><p>The frontend is where fans interact with the API. Built with simplicity and functionality in mind Leveraging <strong>S3</strong> and <strong>CloudFront</strong>, it offers:</p><ol><li><strong>NFL Schedule Display</strong>: Users can view the latest game schedules.</li><li><strong>Poll for Updates</strong>: A button allows users to refresh the schedule on demand, instantly fetching new data from the API.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0C0NBRzGhQZ1vYr9B8W64A.png" /></figure><h3>How It All Comes Together</h3><ol><li><strong>API Deployment</strong>: The API, running on ECS, fetches game schedule from SERPAPI, processes requests, with Docker images managed via ECR.</li><li><strong>Authorization</strong>: Auth0 ensures secure access to the API endpoints.</li><li><strong>Frontend Interaction</strong>: The web UI communicates with the API Gateway, allowing users to fetch and view schedules.</li><li><strong>CI/CD Automation</strong>: GitHub Actions continuously builds and deploys the latest updates to ECR.</li></ol><p>All resources were provisioned and managed with IAC using Terraform, which allows for reusability and consistency.</p><p>This project demonstrates the power of containerized applications and the efficiency of DevOps pipelines. By combining <strong>ECS</strong>, <strong>ECR</strong>, <strong>ALB</strong>, <strong>API Gateway</strong>,<strong>GitHub Actions and Terraform. </strong>I created a scalable, highly available, secure and automated solution. This is how modern cloud tools can bring complex ideas to life like delivering NFL schedules.</p><p>You can find the repository <a href="https://github.com/oyogbeche/containerized_sports_api.git">here</a>,</p><p>Have questions about this project or want to share your thoughts, suggestions or any ideas? You can leave a comment below as well as connect on <a href="https://www.linkedin.com/in/oyameogbeche/">LinkedIn</a> or <a href="https://x.com/oyameogbeche">X</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6d05c5b6cb3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real World Project: Building an NBA Data Lake: From Raw Data to Slam Dunk Insights with AWS]]></title>
            <link>https://medium.com/@oyogbeche/real-world-project-building-an-nba-data-lake-from-raw-data-to-slam-dunk-insights-with-aws-28b8f59f3a2e?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/28b8f59f3a2e</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Wed, 22 Jan 2025 16:12:21 GMT</pubDate>
            <atom:updated>2025-01-22T16:18:45.607Z</atom:updated>
            <content:encoded><![CDATA[<p>Data is the MVP when it comes to making informed decisions, and I recently built an NBA-themed data lake to prove it. Using <strong>AWS S3</strong>, <strong>Glue</strong>, <strong>Athena</strong>, and <strong>Quicksight</strong>, I created a pipeline to fetch, transform, and analyze NBA player data. The highlight? Visualizing insights like how point guards (PG) earn some of the highest salaries in the league. Let’s break it down!</p><h3><strong>Architecture</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KZgqzf0jvGafKB_syZZUFw.jpeg" /></figure><h3>Step 1: Data Collection — The Draft Pick</h3><p>I fetched NBA player data from SportsData.io’s API using Python. The data included player names, salaries, positions, and colleges. This raw data was saved in JSON format and uploaded to an <strong>S3 bucket</strong>.</p><ul><li><strong>Key AWS Service</strong>: <strong>Amazon S3</strong> served as the secure and scalable foundation for our data lake.</li></ul><h3>Step 2: Data Transformation — Coaching the Team</h3><p>Next, I used <strong>AWS Glue</strong> to automate the process of extracting, transforming, and loading (ETL) the data into a structured format.</p><p><em>ETL Process</em>:</p><ol><li><strong>Extract</strong>: Pulled raw JSON data from the S3 bucket.</li><li><strong>Transform</strong>: Reformatted the data into a tabular structure using Glue jobs, categorizing player positions and salaries and dropping null data fields.</li><li><strong>Load</strong>: Saved the transformed data back into the S3 bucket for querying.</li></ol><ul><li><strong>Key AWS Service</strong>: <strong>AWS Glue</strong> streamlined the ETL process, ensuring data was clean and ready for analysis.</li></ul><h3>Step 3: Querying the Data — The Analyst’s Playbook</h3><p>With structured data in place, I used <strong>Athena</strong> to write SQL queries that revealed fascinating insights. One such query analyzed player positions and salaries to find trends in earnings:</p><p>Sample query:</p><pre>SELECT position, AVG(salary) AS avg_salary  <br>FROM nba_players <br>GROUP BY position  <br>ORDER BY avg_salary DESC; </pre><p>The results showed that point guards (PG) consistently earn some of the highest salaries in the league.</p><ul><li><strong>Key AWS Service</strong>: <strong>Amazon Athena</strong> provided a cost-efficient, serverless way to query and analyze the data.</li></ul><h3>Step 4: Visualization — Bringing the Insights to Life</h3><p>To make the insights more digestible, I used <strong>Quicksight</strong> to create visualizations. A bar chart showcased the average salaries of NBA players by position, with point guards leading the pack.</p><p>🔹 <strong>Key AWS Service</strong>: <strong>Amazon Quicksight</strong> brought the data to life with interactive and dynamic visuals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*GUlSS-FCPd6hfAk7WKAiuA.png" /></figure><h3>Final Insights</h3><p>After combining AWS services and NBA data, here’s what I learned:</p><ul><li><strong>Point Guards</strong> lead the league in average salaries, highlighting the premium value placed on leadership and playmaking.</li><li><strong>ETL pipelines</strong> with Glue make transforming raw data incredibly efficient.</li><li>Visualizing data with Quicksight adds depth to the analysis, making it accessible and engaging.</li></ul><h3>Why This Matters</h3><p>This project highlights how AWS services can turn raw data into actionable insights, from ETL processes to interactive visualizations. By leveraging the power of S3, Glue, Athena, and Quicksight, I built a scalable, cost-efficient pipeline that delivers impactful results.</p><p>Are you ready to create your own data-driven solutions? Let’s connect and discuss how AWS can help!</p><p>Have questions about this project or want to share your thoughts, suggestions or any ideas? You can leave a comment below as well as connect on <a href="https://www.linkedin.com/in/oyameogbeche/">LinkedIn</a> or <a href="https://x.com/oyameogbeche">X</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28b8f59f3a2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real World Project: NBA Gameday Notification Service.]]></title>
            <link>https://medium.com/@oyogbeche/real-world-project-nba-gameday-notification-service-5a4f4afa7c37?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a4f4afa7c37</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[devopsallstarschallenge]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Sat, 18 Jan 2025 16:40:20 GMT</pubDate>
            <atom:updated>2025-01-26T01:08:42.864Z</atom:updated>
            <content:encoded><![CDATA[<p>Sports enthusiasts know the thrill of staying updated with their favorite teams — every game, every score, and every highlight matters. Leveraging AWS services, I built an NBA gameday notification service that delivers personalized updates to users via email. Here’s how I combined AWS’s power with Terraform to create an efficient, scalable solution.</p><h4>Project Overview</h4><p>The NBA Gameday Notification Service allows users to:</p><ul><li>Register their email and preferred NBA team via a simple static web application.</li><li>Receive game notifications matched to their selected team directly in their inbox.</li></ul><p>Key components include:</p><ul><li><strong>Frontend:</strong> A static website hosted on Amazon S3 and distributed via CloudFront.</li><li><strong>Backend:</strong> Event-driven architecture using API Gateway, Lambda, DynamoDB, EventBridge, and SES.</li><li><strong>Infrastructure as Code:</strong> Provisioned with Terraform for consistency and reusability.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hQS2BMPGrIxRQN1uCGThA.jpeg" /></figure><h4>Architecture Overview / Detailed Workflow</h4><ol><li><strong>Frontend (User Registration):</strong></li></ol><ul><li>A static website hosted on <strong>Amazon S3</strong> serves as the user interface.</li><li><strong>Amazon CloudFront</strong> acts as the CDN, ensuring fast and secure content delivery.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VPCbmwzn1X7RP410Cl7T9g.png" /></figure><p><strong>2. API and Data Storage:</strong></p><ul><li><strong>Amazon API Gateway</strong> provides endpoints for user registration.</li><li>A <strong>Lambda function</strong> processes user input and stores it in a <strong>DynamoDB table</strong>, including email addresses and preferred teams.</li></ul><p><strong>3. Event-Driven Notifications:</strong></p><ul><li><strong>Amazon EventBridge</strong> triggers a Lambda function every 2 hours.</li><li>This Lambda fetches NBA game data from the SportsData.io API.</li><li>The function compares the game data with user preferences stored in DynamoDB and sends personalized notifications via <strong>Amazon SES</strong>.</li></ul><p><strong>4. Infrastructure as Code:</strong></p><ul><li>The entire infrastructure was provisioned using Terraform modules, ensuring:</li><li>Scalability: Easily add more services without significant architectural changes.</li><li>Reusability: Modules for S3, Lambda, and DynamoDB can be reused in future projects.</li><li>Reliability: Automated provisioning reduces human error.</li></ul><p><strong>Steps to Implement:</strong></p><ol><li><strong>Configured SES:</strong></li></ol><ul><li>Configured Domain name Identity used for email sending.</li></ul><p>2. <strong>Developed Lambda Function:</strong></p><ul><li>Used Python to fetch game day details from the SportsData.io API.</li><li>Processed the data, filtered games according to users preference.</li><li>Trigger SES for email notification.</li></ul><p>3. <strong>Setup EventBridge Rule:</strong></p><ul><li>Created a rule with a 2-hour rate schedule.</li><li>Configured the rule to trigger the Lambda function.</li></ul><p>4. <strong>Setup another Lambda Function:</strong></p><ul><li>Using the microservices approach for easy maintainance, sacalabilty, I used a different Lambda function to handle the user input from the UI.</li><li>This Lambda processed the input and updated the database(DynamoDB).</li></ul><p>5. <strong>Configured API Gateway:</strong></p><ul><li>The API Gateway handles routing traffic to the Lambda function.</li><li>API endpoint for the web UI</li></ul><p>6.<strong> Configured S3 Bucket:</strong></p><ul><li>Provisioned S3 bucket that will store the static content for the static web UI.</li></ul><p>7.<strong> Setup CloudFront Distribution:</strong></p><ul><li>Setup CloudFront distribution network for secured content delivery.</li><li>Used the S3 bucket as the Origin.</li></ul><p>I fall more in love with Infrastructure as Code (IAC) everytime I get to use it. It simplifies the architecture provisioning process, maintenance, reusability and scalability. I was able to write my own modules for this architecture and configuration files, simplifying this whole infrastructure provisioning to just 3 commands.</p><p>You guessed right!</p><pre>Terraform init<br>Terraform plan<br>Terraform apply</pre><p>and within minutes your infrastructure is up and runnig, after playing around with it, to clean up afterwards you can run:</p><pre>terraform destroy</pre><h4>Future Enhancements</h4><ol><li><strong>Real-Time Notifications:</strong> Incorporate WebSocket APIs for instant updates alongside email notifications.</li><li><strong>Expanded Functionality:</strong> Add support for users to login and manage dashboard with AWS Cognito</li><li><strong>User Dashboard:</strong> Develop a dashboard where users can update their preferences and view other updates.</li></ol><p>The NBA Gameday Notification Service showcases the power of serverless and event-driven architectures. By leveraging AWS services like S3, API Gateway, Lambda, DynamoDB, EventBridge, and SES, I built a scalable and user-friendly solution. This project highlights the potential of combining cloud-native tools with Infrastructure as Code to deliver real-world, impactful applications.</p><p>You can find the repository <a href="https://github.com/oyogbeche/nba_gameday_notification.git">here</a>,</p><p>Try out the service <a href="https://d1qnq2dcfhzp5r.cloudfront.net/">here</a>.</p><p>Have questions about this project or want to share your thoughts, suggestions or any ideas? You can leave a comment below as well as connect on <a href="https://www.linkedin.com/in/oyameogbeche/">LinkedIn</a> or <a href="https://x.com/oyameogbeche">X</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a4f4afa7c37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real World Project: Weather Dashboard Service]]></title>
            <link>https://medium.com/@oyogbeche/real-world-project-weather-dashboard-service-bde5c6e485e1?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/bde5c6e485e1</guid>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Tue, 14 Jan 2025 17:13:43 GMT</pubDate>
            <atom:updated>2025-01-14T17:13:43.199Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog post, I’ll walk you through my experience building a weather dashboard that collects real-time weather data using the OpenWeather API. The project not only processes and stores the weather data in an AWS S3 bucket but also integrates best practices like automated testing. This is part of the series #DevOpsAllStarsChallenge.</p><p><strong>Project Overview:</strong></p><p>The goal of the project was to create a system that fetches real-time weather data for multiple cities, processes it, and saves the data in an S3 bucket. I leveraged Python to handle the logic of fetching and processing the data, the OpenWeather API to get weather and forecast information, and AWS S3 as the storage solution. The data saved includes real-time weather metrics and forecast information.</p><p><strong>Tools and Technologies Used:</strong></p><ul><li><strong>Python</strong>: The primary programming language for handling logic.</li><li><strong>OpenWeather API</strong>: A powerful tool that provided real-time weather data and forecasts.</li><li><strong>AWS S3</strong>: Used to store processed weather data for multiple cities.</li><li><strong>GitHub Actions</strong>: for automated testing.</li></ul><p><strong>Challenges Faced and Solutions:</strong></p><ul><li><strong>Writing Unit Tests</strong>: One of the biggest challenges was writing effective unit tests for the logic that fetches data from the OpenWeather API, processes it, and then stores it in an S3 bucket. Since the logic involves external systems (the API and AWS), mocking these services was crucial to ensure that my tests remained isolated.</li><li><strong>Solution: </strong>I used libraries like unittest and mock to simulate API responses and interactions with S3. This allowed me to test my logic without needing to make actual API calls or interact with AWS directly during the test runs.</li><li><strong>Error Handling In Distributed systems: </strong>Dealing with errors in a distributed system like this, where external services are involved, required a robust error handling strategy. API outages, rate limits.</li><li><strong>Solution</strong>: I implemented comprehensive error handling in my code, logging errors for debugging.</li></ul><p><strong>Lessons Learned:</strong></p><ol><li><strong>Integrating External APIs</strong>: One of the most valuable lessons from this project was learning how to interact with external APIs, such as the OpenWeather API. I gained hands-on experience with making API calls, handling API responses, and dealing with rate limiting and error handling.</li><li><strong>Error Handling in Distributed Systems</strong>: This project emphasized the importance of handling errors in a distributed system, where external dependencies can fail at any time. I learned how to create proper Error handling.</li><li><strong>Automated Testing </strong>: I gained experience with setting up CI pipelines using GitHub Actions, which helped me automate my testing and ensure that my code was always in a deployable state.</li><li><strong>Unit Testing for Code Quality</strong>: Writing unit tests was initially challenging, but it helped me identify edge cases and ensure that my code was both correct and stable.</li></ol><p><strong>Conclusion:</strong></p><p>Building this weather dashboard was a rewarding experience. Not only did I learn how to integrate external APIs but I also got hands-on experience with modern software development practices like automated testing and CI. The challenges I faced helped me grow and better understand how to work with these technology.</p><p>You can checkout the repository <a href="https://github.com/oyogbeche/weather-dashboard.git">here</a>, as well as connect on <a href="https://www.linkedin.com/in/oyameogbeche/">LinkedIn</a> or <a href="https://x.com/oyameogbeche">X</a>. Share your thoughts, suggestions or any ideas you may have.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bde5c6e485e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Underutilized AWS Services: EventBridge]]></title>
            <link>https://medium.com/@oyogbeche/underutilized-aws-services-eventbridge-93158afc1c4b?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/93158afc1c4b</guid>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Wed, 08 Jan 2025 22:58:29 GMT</pubDate>
            <atom:updated>2025-01-08T22:58:29.982Z</atom:updated>
            <content:encoded><![CDATA[<p>AWS EventBridge stands as a powerful tool in modern architectures. Yet, despite its versatility, EventBridge often underutilized, overshadowed by more familiar AWS services like SNS, SQS, and Lambda. Today, let’s explore why EventBridge deserves more recognition and how it can enhance your event-driven applications.</p><h4>What is AWS EventBridge?</h4><p>AWS EventBridge is a fully managed event bus service that allows you to connect applications using events. Unlike traditional messaging systems, EventBridge enables seamless communication between AWS services, your applications, and even third-party SaaS applications.</p><h4>Why is EventBridge Underutilized?</h4><p><strong>Misunderstood Purpose</strong>: Many people perceive EventBridge as a mere extension of SNS or SQS, missing its unique capabilities, such as:</p><ul><li>Advanced filtering based on specific event patterns.</li><li>Seamless integration with over 200 AWS services and third-party SaaS tools.</li></ul><p><strong>Overlapping AWS Services</strong>: AWS offers numerous messaging and integration tools (SNS, SQS, Step Functions), creating uncertainity on when to choose EventBridge.</p><p><strong>Complexity in Patterns</strong>: Writing precise event patterns for filtering can feel difficult, especially for newcomers.</p><p><strong>Limited Exposure</strong>: EventBridge is often overshadowed in beginner tutorials or foundational AWS content, leading to underutilization.</p><h4>Why You Should Pay Attention to EventBridge</h4><p><strong>Simplifies Integration</strong>: EventBridge can connect services without manual intervention, allowing for dynamic and automated workflows.</p><p><strong>Enhanced Flexibility</strong>:</p><ul><li>Fine-grained event filtering allows you to route specific events to relevant targets.</li><li>Multiple targets can consume the same event without additional configurations.</li></ul><p><strong>Cross-Account and Cross-Region Event</strong>: Perfect for multi-account AWS setups, EventBridge simplifies sharing events across accounts and regions.</p><p><strong>Event Replay</strong>: With the event replay feature, you can debug systems or backfill data by replaying past events.</p><p><strong>Cost-Effective</strong>: EventBridge’s pay-per-event pricing is suitable for a variety of use cases, from small-scale applications to enterprise-level systems.</p><h4>Key Use Cases for AWS EventBridge</h4><ul><li><strong>Automating Operations</strong>: Automatically trigger workflows for events like EC2 instance state changes or RDS backups.</li><li><strong>Real-Time Monitoring</strong>: Stream application or system events into monitoring pipelines like Datadog or Splunk.</li><li><strong>Cross-Application Communication</strong>: Enable microservices to communicate asynchronously using events.</li><li><strong>Third-Party SaaS Integrations</strong>: Connect AWS services with external tools like Zendesk, Salesforce, or Slack for enhanced productivity.</li><li><strong>IoT and Analytics</strong>: Collect IoT data or analytical events into central processing pipelines.</li></ul><p>AWS EventBridge is more than just a messaging service — it’s a gateway to building robust, scalable, and real-time applications. By embracing its capabilities, you can decouple systems, streamline workflows, and unlock new possibilities for automation and integration. Don’t let its understated presence fool you — EventBridge is a key player in modern cloud architectures. Start exploring its potential today!</p><p>What are your favorite EventBridge use cases? Share your thoughts in the comment below or you can connect on <a href="https://www.linkedin.com/in/oyameogbeche/">LinkedIn</a>, <a href="https://github.com/oyogbeche">GitHub</a>,<a href="https://x.com/oyameogbeche"> X</a> and let’s discuss how to harness its power for your next project!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93158afc1c4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of AWS IAM: Tips for Fine-Grained Access Control]]></title>
            <link>https://medium.com/@oyogbeche/the-power-of-aws-iam-tips-for-fine-grained-access-control-267616defe64?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/267616defe64</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-iam]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[acces]]></category>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Tue, 07 Jan 2025 09:47:41 GMT</pubDate>
            <atom:updated>2025-01-07T20:58:21.590Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*XqpU3F4CoGoeX4XkNMbrWQ.jpeg" /></figure><p>AWS Identity and Access Management (IAM) is the backbone of securely managing access to your AWS resources. While it’s a widely used service, its true power often goes underutilized. Here are some practical tips to help you implement fine-grained access control, reduce risks, and streamline management in your AWS environment.</p><h4>1. Adopt the Principle of Least Privilege</h4><p>Always start with the least privilege and grant only the permissions necessary for a specific task. For example, instead of giving full S3 access, allow only s3:GetObject for a bucket that the user needs to read from. Use AWS managed policies as a starting point but update them to fit your specific requirements.</p><h4>2. Use IAM Groups for Role-Based Access</h4><p>Avoid assigning permissions directly to individual users. Instead, create groups based on roles or responsibilities (e.g., developers, admins, auditors) and assign permissions to these groups. This simplifies permission management as team members come and go.</p><h4>3. Use Service Control Policies (SCPs) in AWS Organizations</h4><p>If managing multiple accounts, SCPs can restrict access at the organization or account level. For example, you can deny the creation of public S3 buckets across all accounts in your organization. You can use this to maintain best practices across accounts.</p><h4>4. Audit and Rotate Access Keys</h4><p>Monitor access key usage regularly using AWS CloudTrail. Rotate keys periodically and disable inactive ones to minimize the risk of compromised credentials.</p><h4>5. Automate with IAM Access Analyzer</h4><p>IAM Access Analyzer helps identify overly permissive policies, ensuring your resources aren’t accessible to unintended entities. Use this tool regularly to audit and refine your permissions.</p><h4>6. Leverage IAM Policies for Granularity</h4><p>Create custom policies that specify:</p><ul><li><strong>Actions</strong>: Define exactly what users can do (e.g., ec2:StartInstances).</li><li><strong>Resources</strong>: Restrict permissions to specific resources (e.g., only a particular EC2 instance or bucket).</li><li><strong>Conditions</strong>: Add constraints like IP addresses, time of day, or MFA requirements.</li></ul><blockquote>Example of a condition-based policy:</blockquote><pre>{<br>  &quot;Version&quot;: &quot;2012-10-17&quot;,<br>  &quot;Statement&quot;: [<br>    {<br>      &quot;Effect&quot;: &quot;Allow&quot;,<br>      &quot;Action&quot;: &quot;s3:GetObject&quot;,<br>      &quot;Resource&quot;: &quot;arn:aws:s3:::example-bucket/*&quot;,<br>      &quot;Condition&quot;: {<br>        &quot;IpAddress&quot;: {&quot;aws:SourceIp&quot;: &quot;203.0.113.0/24&quot;}<br>      }<br>    }<br>  ]<br>}</pre><h4>7. Enforce Multi-Factor Authentication (MFA)</h4><p>Enhance security by requiring MFA for sensitive operations. Use conditional policies to enforce this, ensuring users have an extra layer of protection before accessing critical resources.</p><h4>8. Leverage IAM Roles over IAM Users Credentials</h4><p>Authenticate human users through AWS SSO or <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers.html">IAM role federation</a>. IAM Users have static long lived credentials and are not linked to a centralized Identity provider which is not a security best practice. <strong>Minimize or avoid creating IAM Users for individual people, as federated access is more scalable and secure.</strong></p><p>IAM is more than just a tool to grant or deny access — it’s a powerful framework to enhance security and operational efficiency in your AWS environment. By adopting these tips, you’ll not only safeguard your resources but also establish a scalable and maintainable access control strategy.</p><p>PS: Avoid Static Long Lived Credentials as much as possible</p><p>What’s your experience with IAM in AWS? Have you implemented any innovative IAM strategies? Let’s connect on <a href="https://www.linkedin.com/in/oyameogbeche/">LinkedIn</a>, <a href="https://github.com/oyogbeche">GitHub</a>,<a href="https://x.com/oyameogbeche"> X</a> or Share your thoughts in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=267616defe64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the Power of Tagging in AWS: Why It Matters and How to Do It Right.]]></title>
            <link>https://medium.com/@oyogbeche/unlocking-the-power-of-tagging-in-aws-why-it-matters-and-how-to-do-it-right-b98081a7a277?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/b98081a7a277</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[tag]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-services]]></category>
            <category><![CDATA[resource-management]]></category>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Fri, 03 Jan 2025 21:50:31 GMT</pubDate>
            <atom:updated>2025-01-03T21:50:31.018Z</atom:updated>
            <content:encoded><![CDATA[<p>In the world of cloud computing, managing resources effectively is critical to maintaining a secure, cost-efficient, and scalable environment. AWS provides a lot of cool services and resources, but keeping track of them can quickly become a challenge as your environment grows. This is where tagging your resources comes in, and it is often neglected and overlooked.</p><p><strong>Tagging:</strong> A<strong> </strong>simple yet powerful feature that can transform the way you organize and manage your AWS resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iWgb69zwdHYOTfDVrkPj0w.jpeg" /></figure><p>In this blog post, we’ll explore the importance of tagging in AWS, discuss best practices, and highlight tools that can help you leverage this feature to its full potential.</p><h3>What is Tagging in AWS?</h3><p>Tagging in AWS refers to the practice of assigning metadata to resources using key-value pairs. Each resource in AWS, such as an EC2 instance or an S3 bucket, can be tagged with descriptive identifiers to make it easier to manage.</p><blockquote>Example Tags:</blockquote><blockquote><strong>Key</strong>: Environment | <strong>Value</strong>: Production</blockquote><blockquote><strong>Key</strong>: Project | <strong>Value</strong>: Cloud Resume Challenge</blockquote><blockquote><strong>Key</strong>: Owner | <strong>Value</strong>: Oyame Ogbeche</blockquote><p>Tags are flexible and can be tailored to meet the specific needs of your organization, making them an invaluable tool for resource management.</p><h3>Why is Tagging Important?</h3><p>I will break this down into five(5) core components why tagging is important.</p><h4>1. Resource Organization</h4><p>Tagging provides a clear and logical structure to your AWS environment. By tagging resources based on attributes such as project, environment, or department, you can quickly identify and group resources. This is especially useful in large-scale environments with hundreds or thousands of resources.</p><h4>2. Cost Management</h4><p>AWS billing can quickly become complex, especially in multi-team or multi-project environments. By tagging resources with cost allocation tags (e.g., Project, Department), you can easily track and attribute expenses using AWS Cost Explorer. This ensures accountability and helps in budgeting effectively.</p><h4>3. Security and Compliance</h4><p>Tags also play a vital role in maintaining security and compliance. For instance, tagging sensitive resources with labels like “Confidential” or “PII” enables better monitoring and auditing. Compliance checks can also be automated based on these tags.</p><h4>4. Automation and Resource Management</h4><p>Tags can be leveraged to automate tasks and manage resources efficiently. For example, you can use tags to:</p><ul><li>Stop non-essential resources during off-hours (e.g., DevEnvironment = Staging).</li><li>Apply policies to specific resources via AWS Config or IAM.</li></ul><h4>5. Improved Troubleshooting</h4><p>When issues arise, tags make it easier to pinpoint resource ownership and purpose. For example, an “Owner” tag can help you quickly identify the team or individual responsible for a specific resource.</p><h3>Best Practices for AWS Tagging</h3><h4>1. Define a Standardized Tagging Policy</h4><p>Develop and enforce a standardized tagging policy to ensure consistency across teams. Agree on naming conventions and required tags to avoid duplication or confusion.</p><h4>2. Tag All Resources</h4><p>Tag all resources, including those created automatically by AWS services. You can enforce tagging using Service Control Policies (SCPs) in AWS Organizations.</p><h4>3. Limit the Number of Tags</h4><p>While AWS allows up to 50 tags per resource, it’s best to use only meaningful and relevant tags. Overloading resources with tags can create unnecessary clutter.</p><h4>4. Use Tags for Automation</h4><p>Incorporate tags into your automation scripts and workflows. For example, AWS Lambda functions can execute tasks based on specific tags.</p><h4>5. Regularly Audit Tags</h4><p>Schedule regular audits to review and clean up tags. This ensures that your tagging remains consistent and up to date.</p><h3>AWS Tools for Managing Tags</h3><p>AWS offers several tools to help you manage tags effectively:</p><ol><li><strong>AWS Tag Editor</strong>: Search and update tags across multiple resources from a single interface.</li><li><strong>AWS Cost Explorer</strong>: Analyze costs based on specific tags, enabling better financial tracking.</li><li><strong>AWS Resource Groups</strong>: Group resources based on tags for streamlined management and operations.</li><li><strong>Lambda Functions: </strong>You can also leverage Lambda functions to automatically tag resources after they are created.</li></ol><h3>Conclusion</h3><p>Tagging in AWS is not just a nice-to-have feature; it’s a necessity for effective cloud resource management. Whether you’re tracking costs, maintaining security, or automating tasks, a robust tagging strategy can make all the difference.</p><p>By implementing best practices and leveraging AWS’s tagging tools, you can ensure your environment is organized, cost-efficient, and scalable. So, start tagging today and unlock the full potential of your AWS environment!</p><p>What’s your experience with tagging in AWS? Have you implemented any innovative tagging strategies? Let’s connect on <a href="https://www.linkedin.com/in/oyameogbeche/">LinkedIn</a>, <a href="https://github.com/oyogbeche">GitHub</a>,<a href="https://x.com/oyameogbeche"> X</a> or Share your thoughts in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b98081a7a277" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MY AWS CLOUD RESUME CHALLENGE!]]></title>
            <link>https://medium.com/@oyogbeche/my-aws-cloud-resume-challenge-4f2c6e396398?source=rss-f628a267b4db------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f2c6e396398</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Oyame Ogbeche]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 18:40:54 GMT</pubDate>
            <atom:updated>2024-11-09T08:46:15.708Z</atom:updated>
            <content:encoded><![CDATA[<p>I came across the AWS Cloud Resume challenge over the internet while researching on cloud projects to help sharpen my cloud skills and experience. I can tell you for a fact I really enjoyed working on this project so much. It is a unique and practical project that allows cloud enthusiasts to apply their skills by building a fully functional Resume website hosted on a Cloud Platform. If you are new to cloud or just looking for a challenge to test some of your cloud skills, I will recommend you take a swing at it as well. I am a certified AWS Solutions Architect and I&#39;m really passionate about cloud and it’s future. I have been studying DevOps Engineering and this was a great way to put my knowledge to a test. Let me walk you through a detailed breakdown how I tackled this challenge.</p><h3><strong>PROJECT OVERVIEW</strong></h3><p>The challenge required me to build a static website for my resume, create a visitor counter using AWS services, and manage the entire infrastructure using infrastructure-as-code tools. The final result includes:</p><ul><li>A static resume website hosted on S3 and served via CloudFront.</li><li>A serverless backend using AWS Lambda and API Gateway to track visitor counts.</li><li>Storing visitor counts using DynamoDB.</li><li>Infrastructure deployment using Terraform.</li><li>Automation with GitHub Actions.</li></ul><p>Here is what my infrastructure looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qQ6vMh08lk3Zw7L9-aw6Zw.jpeg" /></figure><h3><strong>FRONTEND(STATIC WEBSITE)</strong></h3><p>The frontend of my project is a simple static HTML/CSS website, which showcases my resume. Studying Cloud Engineering at AltSchool Africa, I also learnt HTML/CSS and I was excited to put that knowledge into use here. I wrote my html code for my resume website and designed it with CSS. I stored the files in an S3 bucket, which AWS S3 serves as a static site. To ensure fast delivery at low Latency, I used CloudFront as a CDN, which caches and serves the content globally at Edge Locations. I also proceeded to registering a domain name (oyameogbeche.cloud) for my resume website with NameCheap domain registrar. I configured NS records with Route53 and also a TLS/SSL certificate with AWS Certificate Manager for secure HTTP connection(HTTPS). I created Route53 A record routing my resume website to the CloudFront distribution.</p><h3><strong>BACKEND(VISITOR COUNT)</strong></h3><p>Part of of this challenge is to be able to track visitors on the website, to do this we need a backend infrastructure which includes a Database. For this project I used AWS DynamoDB which is a NoSQL database to store visitor’s count. To update and retrieve the visitor’s count from the database, I use AWS Lambda Function which is serverless. The Lambda function contains Python code which is used in executing a database query. This serverless setup ensures auto scalability without any need for manual infrastructure management.</p><h3><strong>API CALLS FROM FRONTEND TO BACKEND</strong></h3><p>At this point, frontend and the backend are not connected, and I need a way to be able to make API calls from our website to the database where I stored the visitor’s count data. As a best practice to not expose my database on the internet, I used an API Gateway to make HTTP API calls from my website to the Lambda function which then invokes the Lambda function to Query the database to get and update the visitor’s count.</p><h3><strong>CI/CD WITH GITHUB ACTIONS</strong></h3><p>One of the core concepts of DevOps is Automation. The ability to automate processes without having to do them manually and avoid human errors as much as possible. In this part of the project I used GitHub Actions to automate deployments of my website files to my S3 bucket, whenever I make changes to them. Also seeing that my website is a static website and CloudFront caches the content at Edge locations for a stipulated amount of time before it checks the origin server for any update. This can be controlled by the TTL (Time To Live) settings. So I also use GitHub Actions to automate CloudFront Invalidations so my changes can be updated immediately.</p><h3><strong>INFRASTRUCTURE AS A CODE (IAC)</strong></h3><p>Just like I mentioned above, one of the core concepts of DevOps is automation, So instead of manually creating AWS resources, I used Terraform to manage the infrastructure. This allowed me to write reusable, version-controlled code that can create or destroy my environment with ease. I configured S3, Lambda, API Gateway, DynamoDB, IAM Policies and IAM Role in my Terraform scripts. Also as a best practice I configured my terraform state file to use remote state. I stored my state file in S3 bucket and used DynamoDB for state locking.</p><h3><strong>CHALLENGES FACED</strong></h3><p>While working on this project , I faced a couple of challenges at some point. Some of this challenges include;</p><ul><li>Setting up the right AWS CLI Profile for terraform</li><li>Initializing the terraform backend for remote state</li><li>Routing DNS from NameCheap</li></ul><p>I always get a little excited when i run into errors, mostly because this presents a learning opportunity, extensive research to be able to fix this errors and improve my skills. It is always worth it at the end. 😊</p><h3><strong>KEY TAKEAWAYS</strong></h3><p>Completing the Cloud Resume Challenge was an invaluable experience. I gained hands-on experience and also improved my skills with Terraform and GitHub Actions. I learned how to automate cloud infrastructure. Beyond technical skills, this project taught me how to troubleshoot cloud configurations and how important it is to thoroughly plan and test cloud infrastructure before deploying.</p><ul><li><a href="https://oyameogbeche.cloud/">My resume link</a></li><li><a href="https://github.com/oyogbeche/AWS-Resume-Challenge.git">GitHub Repo</a></li></ul><p>Thank you for stopping by , If you have any questions or suggestions please feel free to drop a comment or you can reach out to me on my socials.</p><ul><li><a href="https://www.linkedin.com/in/oyameogbeche">LinkedIn</a></li><li><a href="https://github.com/oyogbeche">GitHub</a></li><li><a href="https://x.com/oyameogbeche">X</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f2c6e396398" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>