<?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 Donovan Brown on Medium]]></title>
        <description><![CDATA[Stories by Donovan Brown on Medium]]></description>
        <link>https://medium.com/@donovan.brown_75022?source=rss-d067154d13bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*z8qPaj29Wr0HMOn_CIqKew.jpeg</url>
            <title>Stories by Donovan Brown on Medium</title>
            <link>https://medium.com/@donovan.brown_75022?source=rss-d067154d13bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:47:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@donovan.brown_75022/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[My Experience During KodeKloud’s Free Learning Week]]></title>
            <link>https://medium.com/@donovan.brown_75022/my-experience-during-kodeklouds-free-learning-week-adbb8e902784?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/adbb8e902784</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kodekloud]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Mon, 16 Feb 2026 16:06:00 GMT</pubDate>
            <atom:updated>2026-02-17T16:03:20.187Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Mtc_s5ZoGwjd_Tzz1F0eA.png" /></figure><p>In this post, I’m going over my experience using the KodeKloud training platform, where you can practice and learn cloud computing, DevOps, and AI skills through video modules and hands-on labs.</p><p>KodeKloud ran a free membership week from February 10 to February 17, 2026. As someone actively building cloud skills, this was an opportunity I couldn’t pass up.</p><p>When you first sign up for the free learning week, you’re greeted with a dashboard that gives you several options to explore:</p><ul><li>Choose Your Track and Courses</li><li>Practice with Hands-on Labs</li><li>Learn Anytime Anywhere with the Mobile App</li><li>Build Job-Ready Skills (KodeKloud Engineer — 100 Days of DevOps/Cloud Challenge)</li><li>KodeKey: One Key, Many AI Models</li><li>Learn by Doing: Lab Courses</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8oimtOZT3jiiebhE5S7jyw.png" /></figure><h3>Choose Your Track and Courses</h3><p>If you’ve used any online learning platform before, this section will feel familiar. You select a topic from a large course library and go through structured lessons.</p><p>The format is usually:</p><ul><li>Reading materials</li><li>Instructor-led video lessons with slides</li><li>Integrated hands-on labs</li></ul><p>The labs are seamlessly built into the platform. Instead of just watching someone explain something, you’re sometimes dropped into a simulated environment where you solve real problems based on what you just learned.</p><p>They offer tracks for AWS, Azure, Google Cloud, DevOps tools, and more. I personally explored the AWS basics track to get a feel for how everything worked. The flow felt smooth and well structured.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8s_MnrFc67Ixh2PjxgRk0Q.png" /></figure><h3>Practice with Hands-On Labs</h3><p>You choose a technology or environment you want to work with, such as Linux, GitHub, Terraform, Python, Docker, DevOps, and more.</p><p>Here’s a quick example of how it works:</p><ol><li>Select Terraform</li><li>Choose a problem (for example, “Manage IAM resources with Terraform”)</li><li>Wait for the environment to spin up</li><li>Follow the instructions</li><li>Solve the lab inside the live environment</li></ol><p>It feels less like studying and more like actually doing the job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O2BFXPTASym2RGxxQVRXXw.png" /></figure><h3>Learn Anytime, Anywhere (Mobile App)</h3><p>There is a mobile app option, but I didn’t explore it much. For a platform this technical and hands-on, I prefer working from a desktop or laptop. It’s just easier to focus and navigate complex environments.</p><p>So I can’t really give a strong opinion on the mobile experience, but it’s nice that the option exists.</p><h3>Build Job-Ready Skills: KodeKloud Engineer (100 Days Challenge)</h3><p>The “100 Days of DevOps/Cloud” challenge gives you real-world scenarios to solve in a lab environment. You earn coins for completing daily challenges, which adds a gamified element.</p><p>The catch? You can only complete one challenge per day unless you use your earned coins to unlock the next one early.</p><p>I like the structure. It encourages consistency and discipline while still giving you the option to move faster if you’re motivated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L6s1cIr3YqosbC1JKFSlLA.png" /></figure><h3>KodeKey: One Key, Many AI Models</h3><p>One feature that really caught my attention was KodeKey.</p><p>A lot of developers struggle with managing multiple AI providers. You have to set up billing accounts, manage different API keys, and integrate separate SDKs. It can get messy fast.</p><p>KodeKey simplifies this by giving you a single unified key that grants access to multiple powerful AI models like GPT-4o, GPT-4.1, Claude Sonnet 4, Gemini 2.5 Pro, and Grok 3. Instead of juggling multiple accounts and payment setups, you generate one key and start building.</p><p>There’s no complicated approval process or credit card setup just to experiment. It’s designed as a learning and prototyping environment, not production use. Think of it as an AI lab where you can safely explore and compare models in real time.</p><p>Security is also addressed. API keys are encrypted, can be rotated easily, and your prompts are not stored or used for training. You also get real-time usage monitoring so you can track your credits and know exactly where you stand.</p><p>If you want more usage, there’s an AI Plan upgrade that increases limits and gives priority support.</p><p>Overall, it’s a clever way to remove friction for developers experimenting with AI tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jTL3z7LaBB75ootYs5KH_Q.png" /></figure><h3>Sandbox Environments</h3><p>One thing I almost forgot to mention is the Sandbox Environments.</p><p>KodeKloud offers sandbox environments for:</p><ul><li>AWS</li><li>Azure</li><li>Google Cloud</li><li>AI environments (Claude Code, n8n, MCP, Azure AI, etc.)</li><li>Linux</li><li>Kubernetes</li><li>Containers</li></ul><p>As someone who already understands AWS basics and wants to start building cloud projects publicly, having a sandbox environment reduces risk of a bill from AWS. The downside is that sandbox access requires a paid Pro account, and there are usage limits on storage and bandwidth per service. That makes sense, especially with services like AWS where usage costs real money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DM5Dga6BgAHK-Yxg5DHI-Q.png" /></figure><h3>The AWS Billing Anxiety</h3><p>Let me be honest. One thing that always makes me nervous about working directly in a real AWS account is accidentally running up a surprise bill.</p><p>Yes, you can set billing alerts in AWS. But I would much rather use a low-risk environment where I can experiment freely without worrying about cost overruns.</p><p>I’m considering either:</p><ul><li>Running a local cloud environment like LocalStack</li><li>Using KodeKloud’s sandbox environment</li><li>Or a combination of both</li></ul><p>If you’re a cloud professional reading this and have suggestions for building in the cloud without risking high AWS bills, I’d genuinely love to hear your approach. Drop a comment and let me know your alternatives.</p><h3>Final Thoughts on KodeKloud</h3><p>I won’t lie. The platform is pretty impressive.</p><p>The hands-on labs, the 100-day challenges, and the sandbox environments make it feel practical and career-focused. It’s not just theory. You actually build and troubleshoot.</p><p>I do wish I had more time to take full advantage of the free week. Between full-time work and volunteer commitments, my time was limited. Still, I got a solid understanding of how the platform operates.</p><p>Overall, I think KodeKloud is a strong platform for learning real-world cloud and AI skills. I’m seriously considering becoming a Pro member.</p><p>And if you’re on a similar cloud journey, it might be worth checking out when or if they run another free week.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adbb8e902784" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 11: Cloud Security Basics and Best Practices]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-11-cloud-security-basics-and-best-practices-ea9e4c459a2c?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea9e4c459a2c</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cloud-security]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 22:11:06 GMT</pubDate>
            <atom:updated>2026-01-19T22:11:06.220Z</atom:updated>
            <content:encoded><![CDATA[<p>This week’s module was all about <strong>cloud security</strong>. Less hands-on building and more learning how to <em>protect</em> what we build. It covered best practices, security strategies, and how to think about maintaining a secure cloud environment long-term.</p><p>A lot of this week was lecture- and diagram-heavy, but honestly, that makes sense. Security is one of those things you really want to understand <em>before</em> something goes wrong.</p><h3>The CIA Triad (No, Not That CIA)</h3><p>One of the first concepts we covered was the <strong>CIA Triad</strong>, which has nothing to do with espionage or James Bond. It’s a foundational model used in cybersecurity to protect information.</p><ul><li><strong>Confidentiality</strong><br>Ensures that data is only accessible to people or systems that are authorized to see it.</li><li><strong>Integrity</strong><br>Makes sure data is accurate, trustworthy, and hasn’t been altered without permission.</li><li><strong>Availability</strong><br>Ensures systems and data are accessible when users need them.</li></ul><p>These three principles guide how data is protected across IT and cloud systems.</p><h3>Authentication vs Authorization (Easy to Mix Up)</h3><p>These two sound similar, and can be very easy to confuse them at first.</p><ul><li><strong>Authentication</strong><br>Proves <em>who you are</em>. Think username, password, or MFA.</li><li><strong>Authorization</strong><br>Determines <em>what you’re allowed to do</em> after you’ve logged in.</li></ul><h3>Common Authentication Methods</h3><ul><li><strong>Passwords</strong> — The most basic form of identity verification.</li><li><strong>Multi-Factor Authentication (MFA)</strong> — Adds an extra step like a phone code or app prompt.</li><li><strong>Biometrics</strong> — Uses fingerprints, facial recognition, or retina scans.</li><li><strong>Certificates</strong> — Digital credentials used for secure machine-to-machine communication.</li></ul><p>In AWS, a great example of authentication is <strong>IAM users and roles</strong>, where each identity has its own credentials.</p><h3>Authorization &amp; Access Control</h3><p>Once authenticated, authorization decides what access a user or service gets.</p><h3>Access Control Types</h3><ul><li><strong>Role-Based Access Control (RBAC)</strong><br>Permissions are assigned based on job roles.</li><li><strong>Attribute-Based Access Control (ABAC)</strong><br>Access is granted based on attributes like tags, department, or environment.</li><li><strong>Policy-Based Access Control</strong><br>Uses written policies to define what actions are allowed or denied.</li></ul><h3>AWS Implementations</h3><ul><li><strong>IAM Policies</strong> — Define what actions are allowed or denied.</li><li><strong>Resource Policies</strong> — Attach permissions directly to resources like S3 buckets.</li><li><strong>Security Groups</strong> — Control network access to AWS resources.</li></ul><h3>Security Controls: Building Multiple Layers of Defense</h3><p>Security controls act like layers of protection. Think fences, locks, cameras, and alarms working together.</p><h3>Preventive Controls</h3><p>Designed to stop problems before they happen:</p><ul><li><strong>Firewalls</strong> — Block unwanted network traffic.</li><li><strong>Encryption</strong> — Protects data by making it unreadable without a key.</li><li><strong>Multi-Factor Authentication</strong> — Adds another barrier to account access.</li></ul><p>These are especially critical for industries like banking and healthcare.</p><h3>Detective Controls</h3><p>Help you <em>notice</em> when something goes wrong:</p><ul><li><strong>Log Monitoring</strong> — Tracks activity across systems.</li><li><strong>Intrusion Detection</strong> — Identifies suspicious behavior.</li><li><strong>Security Auditing</strong> — Reviews configurations and access patterns.</li></ul><h3>Corrective Controls</h3><p>Kick in <em>after</em> something breaks:</p><ul><li><strong>Backup and Recovery</strong> — Restores lost or damaged data.</li><li><strong>Incident Response</strong> — Steps taken to contain and fix breaches.</li><li><strong>Auto Patching</strong> — Automatically fixes known vulnerabilities.</li></ul><h3>Risk Assessments in Cloud Computing</h3><p>Risk assessment is the process of identifying potential threats, evaluating their impact, and deciding how to handle them. This helps organizations understand their security posture and prioritize protection efforts.</p><h3>Key Objectives</h3><ul><li>Identify vulnerabilities</li><li>Reduce security risks</li><li>Protect sensitive data</li><li>Maintain business continuity</li></ul><h3>Core Components</h3><ul><li>Asset identification</li><li>Threat analysis</li><li>Risk evaluation</li><li>Mitigation planning</li></ul><h3>Risk Assessment Process</h3><ol><li>Identify assets</li><li>Identify threats</li><li>Assess likelihood and impact</li><li>Apply mitigation strategies</li><li>Monitor and review continuously</li></ol><h3>Network Security in AWS</h3><p>Network segmentation is a big deal in cloud security.</p><p>A <strong>VPC (Virtual Private Cloud)</strong> is your own private section of AWS. You define your own IP ranges, such as 10.0.0.0/16, which gives you over 65,000 IP addresses.</p><p>VPCs can:</p><ul><li>Span multiple Availability Zones</li><li>Support disaster recovery</li><li>Improve resilience and high availability</li></ul><p>AWS allows you to isolate resources and tightly control traffic flow.</p><h3>Network security is a major part of cloud defense.</h3><p>A <strong>VPC (Virtual Private Cloud)</strong> is your own private section of AWS. You define your IP range using CIDR blocks like 10.0.0.0/16, which gives over 65,000 IP addresses.</p><p>AWS allows:</p><ul><li>VPCs across multiple regions for disaster recovery</li><li>Multiple availability zones for high availability</li><li>Full isolation and control over networking</li></ul><p>Network segmentation is used to limit exposure and control traffic.</p><h3>Common Public Subnet Resources</h3><ul><li>Application Load Balancers</li><li>Bastion Hosts</li><li>NAT Gateways</li><li>Web Servers</li></ul><h3>Private Subnet Characteristics</h3><ul><li>No direct internet access</li><li>Controlled outbound access</li><li>Strong access controls</li></ul><h3>NAT Gateway Configuration</h3><ul><li>Allows outbound internet access</li><li>Blocks inbound connections</li><li>Lives in a public subnet</li><li>Requires an Elastic IP</li></ul><h3>Typical Private Resources</h3><ul><li>Application servers</li><li>Databases</li><li>Internal services</li><li>Cache layers</li><li>Backend systems</li></ul><h3>Network Security in AWS</h3><p>Network security is a major part of cloud defense.</p><p>A <strong>VPC (Virtual Private Cloud)</strong> is your own private section of AWS. You define your IP range using CIDR blocks like 10.0.0.0/16, which gives over 65,000 IP addresses.</p><p>AWS allows:</p><ul><li>VPCs across multiple regions for disaster recovery</li><li>Multiple availability zones for high availability</li><li>Full isolation and control over networking</li></ul><p>Network segmentation is used to limit exposure and control traffic.</p><h3>Common Public Subnet Resources</h3><ul><li>Application Load Balancers</li><li>Bastion Hosts</li><li>NAT Gateways</li><li>Web Servers</li></ul><h3>Private Subnet Characteristics</h3><ul><li>No direct internet access</li><li>Controlled outbound access</li><li>Strong access controls</li></ul><h3>NAT Gateway Configuration</h3><ul><li>Allows outbound internet access</li><li>Blocks inbound connections</li><li>Lives in a public subnet</li><li>Requires an Elastic IP</li></ul><h3>Typical Private Resources</h3><ul><li>Application servers</li><li>Databases</li><li>Internal services</li><li>Cache layers</li><li>Backend systems</li></ul><h3>Network Segmentation Best Practices (Easy Version)</h3><ul><li>Separate public and private resources</li><li>Use least-privilege networking rules</li><li>Limit inbound access</li><li>Use bastion hosts or VPNs</li><li>Spread resources across availability zones</li></ul><h3>Data Protection in the Cloud</h3><ul><li>Encrypt data at rest and in transit</li><li>Control access with IAM</li><li>Monitor data access</li><li>Regularly back up critical data</li></ul><h3>AWS Key Management Service (KMS)</h3><p>AWS KMS helps manage encryption keys securely. It allows you to create, rotate, and control access to encryption keys used across AWS services. This removes the burden of manually managing keys and improves security consistency.</p><h3>And finally S3 Bucket Security</h3><ul><li>Block public access by default</li><li>Use bucket policies carefully</li><li>Enable encryption</li><li>Use versioning and logging</li><li>Apply least-privilege permissions</li></ul><h3>Final Thoughts</h3><p>This module was heavier on theory and diagrams, but it was still valuable. I already had some familiarity with concepts like encryption, authentication, and authorization, but seeing everything through an AWS lens was helpful</p><p>The next set of modules looks much more <strong>project-based</strong>, which I’m excited about. After completing 11 weeks in the Cloud Engineers Academy, with plenty of ups and downs balancing work and volunteer commitments, it feels good to be moving into more hands-on application approach.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea9e4c459a2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 10: JavaScript, TypeScript, and Building Cloud Infrastructure with AWS CDK]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-10-javascript-typescript-and-building-cloud-infrastructure-with-aws-cdk-093192d41f7f?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/093192d41f7f</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 19:59:38 GMT</pubDate>
            <atom:updated>2025-12-29T19:59:38.078Z</atom:updated>
            <content:encoded><![CDATA[<p>This week was all about using <strong>JavaScript and TypeScript with the AWS Cloud Development Kit (CDK). </strong>The CDK lets you define cloud infrastructure using real programming languages, which means you’re still doing Infrastructure as Code (IaC), just in a more developer-friendly way.</p><p>If you’re familiar with CloudFormation or Terraform, CDK sits in the same space. The difference is that instead of writing large YAML or HCL files, you write actual code that <em>compiles down</em> into cloud infrastructure templates.</p><h3>Quick Refresh: JavaScript &amp; TypeScript</h3><h3>JavaScript</h3><p>JavaScript is a flexible, widely-used programming language that powers websites, servers, automation tools, and now cloud infrastructure. It’s event-driven, easy to get started with.</p><h3>TypeScript</h3><p>TypeScript is JavaScript with types. It adds structure and safety on top of JavaScript, which helps catch bugs early and makes large projects easier to maintain. In cloud projects, TypeScript is great because infrastructure definitions can get complex quickly.</p><h3>JavaScript &amp; TypeScript Basics Covered</h3><p>This module reviewed some familiar fundamentals:</p><ul><li>const for variable declarations</li><li>Common data types</li><li>if / else statements</li><li>for loops</li><li>while loops</li></ul><p>Nothing too intense here, but important building blocks for working with CDK.</p><h3>What Is the AWS CDK?</h3><p>The <strong>AWS Cloud Development Kit (CDK)</strong> is an open-source framework for defining cloud infrastructure using code. Instead of manually creating AWS resources or writing long templates, you describe your infrastructure using programming constructs.</p><h3>Why CDK Is Cool</h3><p>Supports multiple programming languages:<br>- JavaScript<br>- TypeScript<br>- Python<br>- Java<br>- C#<br>- Go</p><ul><li>Uses <strong>high-level constructs</strong> with sensible defaults</li><li>Encourages <strong>reusable components</strong></li><li>Compiles down to CloudFormation under the hood</li><li>Great for object-oriented and modular infrastructure design</li></ul><h3>What Is a Stack in CDK?</h3><p>A <strong>stack</strong> is a unit of deployment in CDK. It represents a collection of AWS resources that are created and updated together.</p><p>You might have:</p><ul><li>One stack for networking (VPC, subnets)</li><li>One stack for application servers</li><li>One stack for databases</li></ul><p>Stacks can reference each other, be reused with different parameters, and help keep infrastructure organized and modular.</p><h3>Example: Creating an S3 Bucket with CDK</h3><p>Here’s a simple example using <strong>TypeScript</strong> to create an S3 bucket with CDK:</p><pre>import * as cdk from &#39;aws-cdk-lib&#39;;<br>import { Bucket } from &#39;aws-cdk-lib/aws-s3&#39;;<br>import { Construct } from &#39;constructs&#39;;<br><br>export class StorageStack extends cdk.Stack {<br>  constructor(scope: Construct, id: string, props?: cdk.StackProps) {<br>    super(scope, id, props);<br><br>    new Bucket(this, &#39;MyBucket&#39;, {<br>      versioned: true,<br>      removalPolicy: cdk.RemovalPolicy.DESTROY,<br>    });<br>  }<br>}</pre><h3>What’s happening here:</h3><ul><li>Import CDK and S3 libraries</li><li>Create a stack called StorageStack</li><li>Define an S3 bucket with versioning enabled</li><li>Set the removal policy so it deletes when the stack is destroyed</li></ul><h3>Basic CDK Project Structure</h3><p>A simple CDK project usually looks like this:</p><pre>cdk-project/<br>├── bin/<br>│   └── cdk-project.ts<br>├── lib/<br>│   └── storage-stack.ts<br>├── cdk.json<br>├── package.json<br>├── tsconfig.json</pre><ul><li>bin/ bootstraps the app</li><li>lib/ contains your stacks</li><li>cdk.json defines how the app runs</li></ul><h3>Installing AWS CDK</h3><p>Before running any CDK commands, you need to install it globally:</p><pre>npm install -g aws-cdk</pre><p>Confirm the install:</p><pre>cdk --version</pre><h3>Creating a New CDK Project</h3><p>To create a new CDK project:</p><pre>cdk init app --language typescript</pre><p>This scaffolds everything you need to start building infrastructure.</p><h3>CDK Constructs: L1, L2, and L3</h3><p>CDK provides different levels of abstraction:</p><ul><li><strong>L1 Constructs</strong><br>Low-level CloudFormation resources. Very detailed and verbose.</li><li><strong>L2 Constructs</strong><br>Higher-level abstractions with built-in defaults (most commonly used).</li><li><strong>L3 Constructs</strong><br>Opinionated patterns that combine multiple resources into one construct.</li></ul><p>Each level gives you a different balance between control and simplicity.</p><h3>Deploying CDK to AWS</h3><p>Once your infrastructure is defined, deploying is easy:</p><pre>cdk deploy</pre><p>And just like that, your resources are live in AWS.</p><h3>Final Thoughts</h3><p>This week was pretty much a cakewalk thanks to my background in web development. Having experience with JavaScript and TypeScript made the learning curve much smoother. More so, understanding how the CDK commands actually execute and deploy resources.</p><p>JavaScript is everywhere, websites, mobile apps, desktop apps, and now cloud infrastructure. CDK feels very familiar if you’ve worked with frameworks like React.js or Next.js. The imports, structure, and modular approach just make sense.</p><p>The CDK compares to Terraform and CloudFormation. Each has its place, and it mostly comes down to preference. CDK feels natural to me because it lets me think in code instead of templates.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=093192d41f7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 9: A Refresher on Python and Why It Matters in the Cloud]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-9-a-refresher-on-python-and-why-it-matters-in-the-cloud-f982fff74572?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/f982fff74572</guid>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 16:27:36 GMT</pubDate>
            <atom:updated>2025-12-08T16:40:44.925Z</atom:updated>
            <content:encoded><![CDATA[<p>This week’s module was about the fundamentals of the Python programming language. Since I already have a developer background, Python feels pretty natural to me. It’s one of those languages that’s simple enough for beginners but powerful enough to run machine learning pipelines, data workflows, and cloud automation.</p><p>Python is also a big part of cloud computing. You can use it with infrastructure as code tools, AWS SDKs, automation scripts, Lambda functions, and even CI/CD tasks. It’s flexible, readable, and works well with API-heavy environments like AWS.</p><h3>The Foundations</h3><p>This week covered the core programming concepts like:</p><ul><li>Variables</li><li>Comments</li><li>Strings</li><li>String concatenation</li><li>Lists</li><li>Adding and removing list items</li><li>Slicing and sorting</li><li>Indexing</li><li>Dictionaries</li><li>Conditionals and control flow</li><li>Loops</li><li>Functions</li></ul><p>Nothing too wild, but always worth refreshing.</p><h3>How These Concepts Show Up in the AWS Cloud</h3><p>Even though these topics seem like intro-level Python, they actually map nicely to how engineers interact with cloud infrastructure. Here are a few examples:</p><ul><li><strong>Strings</strong><br>For naming AWS resources, building configuration keys, or formatting log messages.</li><li><strong>String concatenation</strong><br>For constructing dynamic names, paths, API endpoints, or structured log outputs.</li><li><strong>Lists</strong><br>Working with collections of resources like EC2 instances, S3 buckets, IP addresses, or AWS regions.</li><li><strong>Adding items to a list</strong><br>Kind of like adding new instances, new configs, or additional resources to a deployment.</li><li><strong>Removing items</strong><br>Mirrors removing unused resources or cleaning up old infrastructure.</li><li><strong>Slicing or sorting</strong><br>Useful for reading subsets of resource data, filtering results, or grabbing the most recent items from an API response.</li><li><strong>Dictionaries</strong><br>Important in the cloud because so much AWS-related data comes back in key-value format. Great for storing structured resource details.</li><li><strong>Conditionals and control flow</strong><br>Used to make decisions based on API responses or validation checks.</li><li><strong>Loops</strong><br>For iterating through large sets of resources, automating bulk tasks, or processing batches of data.</li><li><strong>Functions</strong><br>Allow you to write modular, reusable scripts that can manage configurations, automate resource updates, or process cloud data in a clean and maintainable way.</li></ul><p>Python fits really well into the cloud engineering world because it can orchestrate all these tasks cleanly.</p><h3>Final Thoughts</h3><p>I’ll admit, I thought about skipping this module at first. I understand the programming basics pretty well, and I don’t use Python heavily day-to-day. But I’m glad I didn’t. Going over the fundamentals again helped me understand <em>why</em> Python is such a powerful tool in the cloud and reminded me how commonly it’s used for automation, scripting, and resource management.</p><p>A few years ago I taught myself some Python on Codecademy (great platform if you’re thinking about learning Python), I never finished the full track because work got hectic at that time, it was nice to return to Python with more intention — and with a cloud-focused mindset this time around.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f982fff74572" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 8: Diving Into CI/CD, GitHub Actions, and a Little Lambda Magic]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-8-diving-into-ci-cd-github-actions-and-a-little-lambda-magic-997cf8a1e193?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/997cf8a1e193</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cicd-pipeline]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Mon, 24 Nov 2025 18:42:31 GMT</pubDate>
            <atom:updated>2025-11-26T19:51:51.960Z</atom:updated>
            <content:encoded><![CDATA[<p>Man, I’ve got to tell you… Between attending conferences, leading local tech workshops, and recently getting sick after the Code for Good West Michigan weekend event (There was a nasty bug going around here in Michigan at the time), it’s no surprise my blog entries have slowed down a bit. I guess that’s just how life moves sometimes. The important part is to keep making progress, even if it feels like you’re inching forward at a snail’s pace. So I’m not complaining… well, maybe a little, <em>ha ha!</em></p><p>This week I dove into the world of DevOps, specifically CI/CD pipelines, GitHub Actions, and a bit of AWS Lambda paired with Python. Aside from Lambda, this was all familiar territory for me since I’ve worked with DevOps engineers before. I’ve pushed code into repos where CI/CD pipelines checked my work for bugs or errors, but I had never built a pipeline myself. That has now changed.</p><h3>What is CI/CD?</h3><p>CI/CD stands for <em>Continuous Integration</em> and <em>Continuous Delivery/Deployment</em>. It’s a process that automates building, testing, and deploying software. Developers push code to a repository, and CI/CD tools immediately run tests and checks to make sure everything is working. This reduces human error, speeds up development, and helps keep codebases stable.</p><h3>Getting into GitHub Actions</h3><p>Another fun area I jumped into was GitHub Actions. If CI/CD is the concept, then GitHub Actions is one of the tools that lets you automate it.</p><p>GitHub Actions uses YAML workflows that react to events. These events can be pushes, pull requests, scheduled jobs, releases, or practically anything happening inside a repo. Each workflow has components such as:</p><ul><li><strong>Triggers (events)</strong> — When the workflow should run.</li><li><strong>Jobs</strong> — The tasks being executed.</li><li><strong>Steps</strong> — Commands inside a job.</li><li><strong>Runners</strong> — Virtual machines that run your job.</li><li><strong>Actions</strong> — Reusable units of automation created by GitHub or the community.</li></ul><h3>Building a GitHub Actions Workflow for Lambda</h3><p>One of my lessons involved creating a GitHub Actions workflow that deploys to AWS Lambda. Every time I push changes to the Lambda function’s folder, the workflow kicks in.</p><p>We stored sensitive AWS access keys inside GitHub Secrets so we could authenticate securely. Once the workflow starts, GitHub Actions uses a runner to install dependencies, package the Lambda function, and deploy it to AWS.</p><p>The folder and file setup looked something like this:</p><p>repo/<br>│<br>├── .github/<br>│ └── workflows/<br>│ └── deploy-lambda.yml<br>│<br>├── lambda_function/<br>│ └── app.py<br>│<br>└── requirements.txt<br>Simple, clean, and easy to maintain.</p><h3>A CloudFormation Pull Request Workflow</h3><p>The second part of the lesson was creating a GitHub Actions workflow that validates and tests a CloudFormation template whenever a pull request is opened or updated.</p><p>This workflow validates the template first. If everything checks out, it deploys a temporary S3 bucket using CloudFormation. After deployment, the pipeline runs tests to confirm the bucket exists and behaves as expected. When everything looks good, it also includes a cleanup step to delete the test stack.</p><p>To trigger it, you just create a branch, make a small change, push it, open a pull request, and watch the automation do the heavy lifting.</p><h3>Final Thoughts</h3><p>Back when I worked with CI/CD pipelines, I only interacted with them by pushing code. I never actually built one myself. So being on the other side of this process — designing workflows, setting up triggers, packaging Lambda functions, validating templates — felt like seeing the gears turn inside a machine I had used for years. And honestly, it was pretty cool. Setting things up manually helped me understand the level of automation that DevOps tools provide and gave me a deeper appreciation for how much time they save. I can definitely see myself continuing to refine and expand on this as I go.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=997cf8a1e193" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 7 — Terraform, IaC, and Why It Just Clicks]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-7-terraform-iac-and-why-it-just-clicks-47f4b4275e69?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/47f4b4275e69</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Thu, 16 Oct 2025 00:29:29 GMT</pubDate>
            <atom:updated>2025-10-17T19:38:37.074Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 7: Terraform, IaC, and Why It Just <em>Clicks</em></h3><p>This week was <em>way</em> overdue. After speaking at the <strong>Digital Empowerment Summit 2025</strong> (which was an incredible experience), I got hit with a brutal case of sinus issues (Once again 😭). Michigan odd weather did its odd Michigan weather thing, and if you’re from here — you already know that battle.<br>And I’m someone who just <em>can’t</em> self-study properly when sick, learning technical concepts while being in an uncomfortable state do <strong>not</strong> mix for me. So I gave myself a break to recover proper… And now I’m back.</p><h3>Diving Back In: Terraform &amp; Infrastructure as Code</h3><p>This week was all about <strong>Terraform</strong> and <strong>Infrastructure as Code (IaC)</strong> — and honestly, this is right in my comfort zone as a developer.</p><p>IaC basically means treating your infrastructure like software. Instead of clicking buttons in the AWS console, you’re writing files that define things like:</p><ul><li>Virtual Machines</li><li>Networks</li><li>Databases</li><li>Load Balancers</li></ul><p>It’s automation, version control, collaboration — all the stuff that makes environments scalable and predictable.</p><h3>Why Is IaC Great?</h3><ul><li><strong>Consistency</strong> — Every environment is created the same.</li><li><strong>Automation</strong> — Environments can be spun up automatically.</li><li><strong>Repeatability</strong> — Deploy staging and production using the same exact config.</li><li><strong>Version Control</strong> — Roll back your entire infrastructure like you roll back code.</li></ul><h3>Terraform vs CloudFormation (My Take)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*93fCs3ySU5iGbkm7_qSRAA.png" /></figure><p>CloudFormation felt powerful but verbose — lots of code for simple things. Terraform felt cleaner and more readable, especially in bigger projects.</p><h3>Providers in Terraform (The Bridge Between You &amp; the Cloud)</h3><p>In Terraform, <strong>providers</strong> are plugins that allow Terraform to interact with different platforms (like AWS, Azure, GitHub, etc.). They handle the low-level API communication for you.</p><p>For example, using the AWS provider:</p><pre>provider &quot;aws&quot; {<br>  region = &quot;us-east-1&quot;<br>}</pre><h3>Basic Terraform EC2 Example</h3><p>Here’s a super simple Terraform config to launch an EC2 instance:</p><pre>resource &quot;aws_instance&quot; &quot;my_server&quot; {<br>  ami           = &quot;ami-0c55b159cbfafe1f0&quot;  # Example Amazon Linux 2 AMI<br>  instance_type = &quot;t2.micro&quot;</pre><pre>  tags = {<br>    Name = &quot;TerraformEC2&quot;<br>  }<br>}</pre><h3>Common Terraform Commands</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jd1mHuHxGQbwSfLutkYpCg.png" /></figure><h3>Terraform Workflow: Launching on AWS</h3><ol><li><strong>Write Code</strong> → Define VPC, EC2, S3, etc.</li><li><strong>Init</strong> → terraform init (download providers)</li><li><strong>Plan</strong> → terraform plan (see what will change)</li><li><strong>Apply</strong> → terraform apply (launch!)</li><li><strong>Destroy</strong> → terraform destroy (clean teardown)</li></ol><h3>Project Structure Best Practices</h3><pre>my-terraform-project/<br>├── main.tf      # Main resources<br>├── variables.tf # Inputs<br>├── outputs.tf   # Outputs (like IPs)<br>├── providers.tf # Cloud provider setup</pre><h3>Deploying a Next.js App via Terraform</h3><p>One of the coolest wins this week — I used Terraform to deploy a <strong>Next.js app on AWS</strong>. Watching an app go live using code-only infrastructure felt Great. Less clicking. More building.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oo4dgVSL66IyOcGGI19geQ.png" /></figure><h3>A Bit of Terraform Struggles</h3><p>I did hit some bumps. At one point, Terraform was yelling at me to deploy in <strong>Japan (ap-northeast-1)</strong> for no reason while I’ve been using <strong>us-east-1</strong> in AWS. Turned out to be a misconfigured region.</p><p>Thankfully, Terraform error messages are <strong>detailed</strong>, so with a little Googling and double-checking my config, I fixed it.</p><h3>Final Thoughts</h3><p>I’m already liking Terraform more than CloudFormation. The syntax is cleaner, modular, and easier to organize. CloudFormation is powerful, but once stacks get long, it’s easy to get lost.</p><p>Terraform feels like <em>real engineering</em> — I can structure modules, separate environments, and keep everything clean and scalable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47f4b4275e69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 6: IAM, VPC Diagrams, and My First Steps with CloudFormation]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-6-iam-vpc-diagrams-and-my-first-steps-with-cloudformation-125adade38dd?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/125adade38dd</guid>
            <category><![CDATA[cloud-engineering]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cloud-services]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Mon, 18 Aug 2025 00:35:25 GMT</pubDate>
            <atom:updated>2025-08-18T00:35:25.152Z</atom:updated>
            <content:encoded><![CDATA[<p>This week was a big one. I got hands-on with <strong>IAM (Identity and Access Management)</strong>, designed a <strong>VPC diagram</strong>, tinkered with <strong>inbound/outbound rules</strong>, and dipped my toes into <strong>Infrastructure as Code (IaC)</strong> using <strong>AWS CloudFormation</strong>. Starting to piece together what a AWS environment looks like.</p><h3>IAM: Identity and Access Management</h3><p>IAM is AWS’s way of controlling <strong>who can do what</strong> in your cloud environment. At first, it felt like just another security feature, but the more I dug in, the more I realized how critical it is — especially as your AWS setup grows.</p><p>Here are the basics, broken down simply:</p><ul><li><strong>Users</strong> → Individual accounts for people who need access.</li><li><strong>Groups</strong> → Collections of users (e.g., a “Developers” group).</li><li><strong>Roles</strong> → Temporary access for services or users. For example, an EC2 instance might assume a role to access S3.</li><li><strong>Permissions/Policies</strong> → Rules that define what actions are allowed (or denied).</li><li><strong>Identity Federation</strong> → Letting users from outside systems (like your company’s login system) access AWS without making new IAM accounts.</li></ul><p>The golden rule of IAM is the <strong>principle of least privilege</strong> → only give people (or services) the exact access they need, and nothing more. And yes, IAM also supports <strong>MFA (multi-factor authentication)</strong> for an extra layer of security.</p><h3>Designing a VPC (and Why I Skipped NAT)</h3><p>I created a VPC and diagrammed it out. You can build a VPC in several ways:</p><ul><li><strong>Manually in the AWS console</strong> → Picking your CIDR blocks, subnets, route tables, and attaching an internet gateway.</li><li><strong>Programmatically (IaC)</strong> → Using tools like CloudFormation (more on that later).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6vmCrqAIfb8Uzv14UF2h0g.png" /><figcaption>VPC Diagram</figcaption></figure><p>You may notice my VPC diagram didn’t include a <strong>NAT Gateway</strong>. That’s because NAT Gateways cost money, and for learning purposes, I didn’t feel like racking up a surprise AWS bill. Instead, I went with a <strong>Bastion Host</strong>.</p><h3>Bastion Host Setup</h3><p>A <strong>Bastion Host</strong> is basically a secure middleman server you SSH into first before connecting to private instances inside your VPC.</p><p>For me:</p><ul><li>I spun up a Bastion Host in a public subnet.</li><li>From my Mac, I connected via SSH using the Bastion’s public IP.</li><li>From there, I was able to “jump” into private EC2 instances and even ping them.</li></ul><p>This setup gave me secure access without opening up my private instances directly to the internet.</p><h3>Inbound and Outbound Rules</h3><p>Another “aha” moment this week was learning how <strong>inbound and outbound rules</strong> actually shape how EC2 instances communicate.</p><p>Here’s the super-simplified version:</p><ul><li><strong>Inbound rules</strong> → What traffic is allowed <em>into</em> your instance. (Example: allow ICMP for ping, or port 22 for SSH).</li><li><strong>Outbound rules</strong> → What traffic can <em>leave</em> your instance. By default, outbound is usually open, but you can lock it down if you want tighter security.</li></ul><p>Once I set these up correctly, I was able to ping my EC2 instance from my Bastion Host, which was a nice little victory.</p><h3>Infrastructure as Code with CloudFormation</h3><p>Now here’s where it got really interesting: <strong>Infrastructure as Code (IaC)</strong>. Instead of clicking around in the AWS Console, you define your infrastructure in a <strong>YAML or JSON file</strong> and let AWS set it up for you.</p><p>Why this is awesome:</p><ul><li>Automation → No more manual clicking around.</li><li>Consistency → Every environment looks exactly the same.</li><li>Speed → Deploy a VPC, EC2s, S3 buckets, and more with one file.</li><li>Version control → Track infrastructure changes like you track code.</li></ul><p>Some of the things I built in my CloudFormation experiments:</p><ul><li>A VPC with public and private subnets</li><li>EC2 instances (with storage, ELB, and Auto Scaling)</li><li>IAM users, groups, and roles</li><li>A Bastion Server</li><li>An S3 bucket (I even launched a simple static website on it)</li><li>An RDS instance</li></ul><p>Of course, it wasn’t all smooth sailing. Writing YAML for the first time had me tripping over indentation errors and typos. A single misplaced space can break your whole template. Pro tip: <strong>install a YAML plugin in VS Code</strong> — it saves a ton of headache.</p><p>When my files failed, I’d see those dreaded red X’s in the AWS Console, forcing me to delete the failed stack or update it after fixing the errors. Painful, but part of the learning curve.</p><p>Here are a few common CloudFormation commands I found helpful:</p><ul><li>aws cloudformation create-stack — stack-name myStack — template-body file://template.yaml</li><li>aws cloudformation update-stack — stack-name myStack — template-body file://template.yaml</li><li>aws cloudformation delete-stack — stack-name myStack</li><li>aws cloudformation describe-stacks — stack-name myStack</li></ul><h3>⚠ Struggles with YAML</h3><p>Now, let me be real — I definitely hit some bumps. This was my first time writing YAML files, and it’s tricky than I expected. A single space or indentation error can cause the whole thing to fail:</p><ul><li>Use a <strong>YAML VS Code plugin</strong> or formatter to catch mistakes early.</li><li>Don’t panic when you see <strong>red X’s</strong> in the console after deploying — just check the logs for typos or missing properties.</li><li>Sometimes you need to <strong>delete or update a stack</strong> after fixing errors and try again.</li></ul><p>It was frustrating at times, but honestly, it also felt rewarding once I finally got a stack to deploy successfully.</p><h3>Final Thoughts</h3><p>This week felt like a real step forward. IAM gave me the tools to <strong>control who can do what</strong>, VPC design taught me how to <strong>structure a network securely</strong>.</p><p>I made mistakes, broke a few YAML files, and had to backtrack more than once — but every red X was a chance to learn.</p><p>I’ll be building on these concepts even more — and hopefully spending less time debugging YAML formatting errors Ha, ha!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=125adade38dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 5: Diving Into AWS Global Infrastructure and Core Networking Fundamentals]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-5-diving-into-aws-global-infrastructure-and-core-networking-fundamentals-8185a4187779?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/8185a4187779</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-services]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Mon, 18 Aug 2025 00:34:20 GMT</pubDate>
            <atom:updated>2025-08-18T00:34:20.366Z</atom:updated>
            <content:encoded><![CDATA[<p>Another week in my cloud journey. This week was all about <strong>AWS global infrastructure</strong> and some of the core networking fundamentals that make the cloud actually work.</p><h3>AWS Global Infrastructure</h3><p>AWS is designed to be available <strong>24/7 anywhere in the world</strong>, and the way they make that possible is through their <strong>global infrastructure</strong>.</p><p>Here’s how it breaks down:</p><ul><li><strong>Regions:</strong> Think of these as clusters of data centers in a specific geographic area (e.g., <em>us-east-1 in Virginia</em> or <em>eu-west-1 in Ireland</em>). If one region goes down, others aren’t affected.</li><li><strong>Availability Zones (AZs):</strong> Within each region are multiple AZs — separate data centers that work together but are independent enough that if one has issues, the others keep running.</li><li><strong>Local Zones: </strong>Smaller, localized zones closer to users for low-latency applications (like gaming or video streaming).</li></ul><p>Basically, AWS has built a massive network of global “power stations” that keep applications running no matter where you or your users are.</p><h3>VPC: Your Own Private Network in the Cloud</h3><p>A <strong>VPC (Virtual Private Cloud)</strong> is like your own private, isolated network inside AWS. It’s where your applications, databases, and services live. You control the setup, the IP addresses, the routing — everything.</p><p>Here are the key building blocks I learned:</p><h3>CIDR Blocks</h3><ul><li>CIDR blocks define the IP address range for your VPC.</li><li>Every resource inside your VPC (EC2, databases, etc.) gets an IP from this range.</li><li>Example: 10.0.0.0/16 gives you a bunch of IPs to work with.</li></ul><h3>Subnets</h3><ul><li>Subnets are <strong>smaller slices of your VPC</strong>.</li><li>You usually split them into <strong>public subnets</strong> (for things like web servers) and <strong>private subnets</strong> (for backend services or databases).</li></ul><h3>Route Tables</h3><ul><li>Route tables control where traffic goes inside your VPC.</li><li>You can customize them to decide what subnets connect to the internet, or to each other.</li></ul><h3>Internet Gateway</h3><ul><li>This is your VPC’s <strong>main door to the internet</strong>.</li><li>If you want a public-facing web app, your VPC needs an internet gateway.</li></ul><h3>NAT Gateway</h3><ul><li>A NAT Gateway allows <strong>outbound internet traffic</strong> for private subnets while blocking unsolicited inbound requests.</li><li>In other words: servers in a private subnet can download updates or reach out to the internet, but outsiders can’t reach in directly.</li></ul><h3>Security Layers in AWS</h3><p>One of the coolest things I learned this week is how AWS stacks multiple layers of security:</p><p><strong>Security Groups</strong></p><ul><li>Act like <strong>firewalls for your EC2 instances</strong>.</li><li>They’re <em>stateful</em>, meaning if you allow incoming traffic, the response traffic is automatically allowed back.</li><li>Example: allow SSH (port 22) for admins, HTTP (port 80) for web users.</li></ul><h3>Network Access Control Lists (NACLs)</h3><ul><li>These operate at the <strong>subnet level</strong>.</li><li>They’re <em>stateless</em>, which means you have to explicitly allow both inbound and outbound rules.</li><li>Think of them as security guards at the subnet entrance, checking every single packet coming in <em>and</em> going out.</li></ul><h3>Wrapping It All Together</h3><p>Here’s how I’d summarize what I learned this week in plain English:</p><ul><li><strong>VPC:</strong> Your own private network in AWS.</li><li><strong>CIDR Blocks: </strong>Define the IP address range of that network.</li><li><strong>Subnets: </strong>Break the network into smaller zones (public/private).</li><li><strong>Route Tables: </strong>Control where traffic flows.</li><li><strong>Internet Gateway: </strong>Lets public traffic in and out.</li><li><strong>NAT Gateway</strong>: Lets private servers go out to the internet, but blocks inbound.</li><li><strong>Security Groups: </strong>Firewalls for individual resources (stateful).</li><li><strong>NACLs: </strong>Firewalls for subnets (stateless).</li></ul><p>When you put it all together, you get a secure, flexible, and reliable environment for your cloud applications.</p><h3>Final Thoughts</h3><p>This week definitely felt like stepping into the “networking” side of cloud computing. Fortunately, I have some knowledge about networking fundamentals so this wasn’t so bad to digest in understanding the concepts</p><p>AWS isn’t just about spinning up servers — it’s about designing secure, reliable architecture where your apps and data live safely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8185a4187779" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 4: Linux, Permissions, and a Bit of S3]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-4-linux-permissions-and-a-bit-of-s3-62f37832ef69?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/62f37832ef69</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-services]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[tehcnology]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 21:25:33 GMT</pubDate>
            <atom:updated>2025-07-21T21:25:33.330Z</atom:updated>
            <content:encoded><![CDATA[<p>This week was all about <strong>Linux basics and file permissions</strong>, which honestly felt like home to me. I’ve always had a soft spot for Linux — it’s one of my favorite operating systems to work in when it comes to coding and development, right next to macOS.</p><h3>A Quick Flashback</h3><p>Back when I first started teaching myself web development and trying to understand how servers work, I had this old, slow laptop that could barely run Windows. So, I wiped it clean and installed <strong>Ubuntu Linux</strong> on it. The awesome thing about Linux is that it’s not computing resource heavy.</p><p>The whole point of installing Ubuntu Linux? To <em>force myself</em> to live in the terminal.</p><p>Linux is super terminal-focused, and if you’re serious about being a developer or going into mid to senior IT type roles, you’ll spend a LOT of time in that black-and-white command line world. Installing Linux was like building muscle memory for navigating files, running programs, setting permissions, and just getting used to how operating systems <em>really</em> work under the hood. I even got into hosting some basic web pages on my own local Ubuntu server back then.</p><h3>Linux in AWS</h3><p>This week, I spun up some <strong>EC2 instances</strong> (AWS virtual machines) and the cool thing is — you can launch them with different Linux-based OS images. Naturally, I looked for Ubuntu first, but ended up going with <strong>Amazon Linux</strong>, which is basically a stripped-down, optimized version of Linux that works perfectly with AWS tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-dKX_8KnPy33JQPj" /></figure><p>Inside the EC2 instance, it was the usual Linux drill:</p><ul><li>Creating and managing files</li><li>Making folders</li><li>Setting file permissions</li><li>Running executables</li></ul><p>This was all very familiar territory for me thanks to my dev/Linux background, and honestly kind of refreshing.</p><h3>File Permissions in Linux</h3><p>One thing that’s essential when working with Linux is <strong>understanding file permissions</strong>. It’s the difference between “everything works” and “why is this not running!?”</p><h3>What Do These Symbols Mean?</h3><p>You’ve probably seen things like:</p><ul><li>-r — r — r —</li><li>-rw-r — r —</li><li>-rwxr — r —</li><li>-rwxr-xr —</li><li>-rwxr-xr —</li></ul><p>Here’s a quick breakdown:</p><ul><li>The first character (-) tells you it’s a file (a d would mean directory).</li><li>Then the rest breaks down like this:</li><li>Owner permissions</li><li>Group permissions</li><li>Others (everyone else)</li></ul><p>So -rwxr-xr — means:</p><ul><li>Owner can read, write, execute</li><li>Group can read and execute</li><li>Others can only read</li></ul><h3>Numeric Mode (AKA the Shortcut Way)</h3><p>If you’re not into memorizing rwxr-xr — , Linux gives you a faster way using numbers:</p><p>Each permission type has a value:</p><ul><li>Read = 4</li><li>Write = 2</li><li>Execute = 1</li></ul><p>Add them up per group:</p><ul><li>644 = Owner can read/write (4+2), Group can read (4), Others can read (4)</li><li>755 = Owner can read/write/execute (7), Group can read/execute (5), Others can read/execute (5)</li></ul><p>To change file permissions, you’d do something like:</p><p>chmod 755 filename.txt</p><h3>Symbolic Mode (When You Want to Be Specific)</h3><p>This is the more “readable” way to change permissions:</p><ul><li>u = User (Owner)</li><li>g = Group</li><li>o = Others</li><li>a = All</li></ul><p>Operators:</p><ul><li>+ adds permission</li><li>- removes permission</li><li>= sets the permission exactly</li></ul><p>Examples:</p><p>chmod u+x script.sh # Add execute for owner</p><p>chmod g-w report.txt # Remove write from group</p><p>chmod a=r document.txt # Everyone gets read-only access</p><h3>Why This Matters</h3><p>Understanding file permissions isn’t just about getting your code to run — it’s a core part of <strong>security</strong>. Accidentally making a file world-writable (hello 777) is a great way to invite trouble.</p><p>So part of being a cloud engineer is learning to:</p><ul><li><strong>Set permissions thoughtfully</strong></li><li><strong>Verify changes with ls -l</strong></li><li><strong>Stick to the principle of least privilege</strong> — give just enough access and no more</li></ul><h3>IAM Roles + S3 = Cloud</h3><p>Now, here’s where things got interesting and new: <strong>attaching an IAM role to an EC2 instance</strong>.</p><p>The goal was to give my EC2 instance <strong>permissions to write to an S3 bucket</strong> — and I pulled it off.</p><p>Here’s a simple breakdown of what I did:</p><p>1. Created an <strong>IAM role</strong> with S3 full access.</p><p>2. Launched an EC2 instance <strong>with that role attached</strong>.</p><p>3. Created a new S3 bucket from the command line using:</p><p><em>aws s3 mb s3://my-bucket-name</em></p><p><em>(“mb” stands for Make Bucket)</em></p><p>4. Made a basic text file inside the EC2 instance.</p><p>5. Used the AWS CLI to push the file into the S3 bucket:</p><p><em>aws s3 cp myfile.txt s3://my-bucket-name</em></p><p>6. Cloud storage in action.</p><h3>Takeaways This Week:</h3><ul><li>Linux feels like home, and being able to use it in the cloud just adds another layer to its power.</li><li>File permissions (read, write, execute) are critical — especially when dealing with secure systems and user access.</li><li>IAM roles are a key concept in AWS for managing what services and instances can access.</li><li>Getting hands-on with CLI tools like aws s3 cp and aws s3 mb made cloud storage feel less abstract and more real.</li></ul><h3>Final Thoughts</h3><p>This week gave me a lot of confidence. While some parts were a refresher, other parts like IAM roles and connecting EC2 to S3 through permissions were brand new — and really cool. It’s exciting to see how the tools I already know, like Linux and the terminal, blend perfectly with cloud technologies.</p><p>Each piece — whether it’s EC2, IAM, or S3 — feels like its own Lego block. And slowly but surely, I’m learning how to snap them together to build real cloud systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62f37832ef69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3, Part 3: Video Upload and Streaming Architecture Works From Creators To Viewers.]]></title>
            <link>https://medium.com/@donovan.brown_75022/week-3-part-3-video-upload-and-streaming-architecture-works-from-creators-to-viewers-12f6540b040b?source=rss-d067154d13bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/12f6540b040b</guid>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-services]]></category>
            <dc:creator><![CDATA[Donovan Brown]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 04:27:12 GMT</pubDate>
            <atom:updated>2025-07-10T04:27:12.380Z</atom:updated>
            <content:encoded><![CDATA[<p>Here is a behind-the-scenes tour of the architecture that powers video upload and streaming experience — from creators to viewers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_rM-hIQpTdh5HEj-d3zdA.png" /><figcaption>Architecture for a video sharing platform</figcaption></figure><h3>Step 1: Creators Upload Videos</h3><p>Everything begins with our users — the content creators.</p><p>When a creator uploads a video, they interact with our <strong>front-end</strong> interface (think: the web app or mobile app), which is backed by <strong>CloudFront</strong> for fast delivery and caching. The uploaded video then gets stored in <strong>Amazon S3</strong> (our trusty file storage).</p><p>We also capture metadata about the upload (title, tags, timestamp, etc.) and save it in <strong>DynamoDB</strong>, a NoSQL database perfect for this kind of data.</p><h3>Step 2: Trigger the Video Processing Engine</h3><p>Once the video is uploaded, the magic begins behind the curtain.</p><p>This is where AWS Lambda and a few key services come into play:</p><ul><li><strong>Lambda Meta Handling</strong>: This function grabs the metadata and orchestrates the next steps.</li><li><strong>Lambda Video Processing</strong>: This function does initial checks, validation, and preparation.</li><li><strong>Elemental MediaConvert</strong>: Converts the uploaded raw video into multiple resolutions (240p, 720p, 1080p, etc.) for smooth streaming across devices.</li><li><strong>Rekognition</strong>: Scans the video for inappropriate content using AI — keeping things clean and safe.</li></ul><h3>Step 3: Store the Converted Videos</h3><p>Once the videos are processed and converted, they’re sent to another <strong>S3 bucket</strong> for long-term storage.</p><p>We also update the <strong>DynamoDB</strong> with new metadata (like resolution options, duration, thumbnail, etc.), and we use <strong>Elasticache</strong> to cache popular videos and metadata for quick access.</p><h3>Step 4: Viewers Stream Videos</h3><p>Now it’s time for viewers to enjoy the content.</p><p>When a user hits play, our <strong>front-end</strong> fetches the video via <strong>CloudFront</strong>, which delivers it lightning-fast from the nearest edge location. The actual video file comes from <strong>S3</strong>, and any needed metadata is pulled from <strong>Elasticache</strong> or <strong>DynamoDB</strong>.</p><p>This means smooth, buffer-free playback for the viewer — just like magic (but powered by solid infrastructure).</p><h3>Summary</h3><p>Here’s a quick recap of the journey:</p><ol><li><strong>Creators upload</strong> videos → Stored in S3 + metadata in DynamoDB</li><li><strong>Lambda functions</strong> orchestrate processing and moderation</li><li><strong>MediaConvert</strong> does the heavy lifting of video conversion</li><li><strong>Rekognition</strong> ensures safety</li><li>Converted videos + metadata go to S3 + DynamoDB</li><li><strong>Viewers stream</strong> videos via CloudFront with data from S3 and Elasticache</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12f6540b040b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>