<?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 Curtis Bartlett on Medium]]></title>
        <description><![CDATA[Stories by Curtis Bartlett on Medium]]></description>
        <link>https://medium.com/@incit3me?source=rss-b5f9871c477a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BcgeepjYPddo9SExUxFXvQ.jpeg</url>
            <title>Stories by Curtis Bartlett on Medium</title>
            <link>https://medium.com/@incit3me?source=rss-b5f9871c477a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:48:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@incit3me/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[AWS Explained Simply — Security Groups vs Network ACLs (NACL)]]></title>
            <link>https://medium.com/@incit3me/aws-explained-simply-security-groups-vs-network-acls-nacl-dfb227b44605?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfb227b44605</guid>
            <category><![CDATA[amazon-web-services]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-security-group]]></category>
            <category><![CDATA[cloud-networking]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 00:17:56 GMT</pubDate>
            <atom:updated>2026-11-02T00:17:56.805Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/729/1*GvruarF22nRfy8SBQuZm3Q.jpeg" /></figure><h3>Understanding Stateful vs Stateless Firewalls in Amazon VPC</h3><p>In our previous article, we talked Amazon Virtual Private Cloud (VPC) and how it allows us to create isolated virtual networks in AWS.</p><p>We learned about public and private subnets, IP addressing and how resources communicate within a VPC.</p><p>So once we created the resources, how do we actually control who has access?</p><p>You launched your EC2 instance that host your companys website but you dont want customers connecting to the admin services or accessing your database.</p><p>This is where Security Groups and Network Acccess Control Lists (NACLs) comes into the picture.</p><p>Both together help control network traffic in Amazon VPC but they do so in different ways.</p><h3>First What is a Firewall</h3><p>Before we talk about Security Groups and NACLs we must understand what a firewall is.</p><p>A firewall helps filter network traffic according to a set defined rules you set.</p><p>Its like a security checkpoint.</p><p>When traffic attempts to enter or leave your environment, the firewall evaluates whether the traffic should be allowed.</p><p>The decision is based on many factors, such as</p><ul><li>Source IP address</li><li>Destination IP address</li><li>Protocols like TCP or UDP</li><li>Port number</li></ul><p>Example, if you are hosting a website, you might allowe HTTPS traffic on TCP port 443 while restricting SSH on TCP port 22 because there is no reason for port 22 to be open.</p><h3>The Apartment Complex</h3><p>Okay, so you live in a luxury apartment with two levels of security.</p><p>At the entrance, theres a bouncer.</p><p>The bouncer checks everyone entering or leaving the propoerty against a list of rules. Some visitors are allowed, and some are denied.</p><p>This bouncer is interesting because he does not remember previous interactions.</p><p>Every time someone tries to enter, he checks the rules again.</p><p>This is what Network ACL looks like.</p><p>Okay, now you entered the apartment complex.</p><p>Now you have to enter the apartment but that does not mean you can automatically enter the apartment.</p><p>Outside your apartment door, theres another security guard.</p><p>This is the guard who controls access to your specific apartment.</p><p>But this security guard, remembers the established interaction from before. Once a connection is authorized, the corresponding return traffic can pass without requiring a seperate permission.</p><p>This is what the Security Group looks like.</p><p>NACLs are stateless while Security Groups are stateful. What makes it easier is that Security groups remember the connection so it keeps track of the state of the connection. NACLs are stateless it does not remember the connection and it does not keep track of the state of the connection.</p><h3>What is an AWS Security Group</h3><p>An AWS Security Group acts as a virtual firewall for AWS resources.</p><p>For example, when you launch an Amazon EC2 instance, you associate Security Groups with its resources.</p><p>These Security Groups determine which network connections are allowed to reach the resource and which outbound connections it can initiate.</p><p>Security Groups have several important characteristics.</p><h3>Security Groups Are Stateful</h3><p>Stateful means that the firewall tracks connection information.</p><p>Okay, a customer connects to your EC2 web server using HTTPS on port 443.</p><p>If the Security Group allows that inbound connection, the corresponding response traffic is automatically permitted, even if a separate outbound rule doesn’t explicitly allow it.</p><p>The Security Group recognizes or remembers the response as part of an authorized connection.</p><p>The same applies in the opposite direction. When an outbound connection is allowed, its corresponding response traffic is permitted back.</p><p>This makes Security Groups easier to manage for many common applications.</p><h3>Security Groups Support Allow Rules Only</h3><p>Security Groups do not have explicit deny rules.</p><p>Instead, you define which traffic is allowed. Traffic that doesn’t match an applicable allow rule is denied.</p><p>For example, a web server Security Group might allow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V7G9MQoThi07mKwsdnUIdA.png" /></figure><p>This configuration allows public HTTPS connections 0.0.0.0/0 while limiting SSH access to a specific address. (Your trusted IP address/32)</p><p>In production environments, SSH access should be tightly restricted, and services such as AWS Systems Manager Session Manager can provide alternatives to exposing SSH.</p><h3>Security Group Rules Are Evaluated Together</h3><p>Unlike NACLs, Security Group rules are not numbered.</p><p>AWS evaluates the rules to determine whether traffic is permitted.</p><p>If an applicable allow rule matches, the traffic is allowed.</p><p>Security Groups are commonly used to enforce access requirements for individual application components, such as web servers and databases.</p><h3>What Is a Network ACL?</h3><p>A Network Access Control List, or NACL, provides an additional layer of network traffic filtering at the subnet level.</p><p>Where Security Groups are associated with network interfaces like EC2, NACLs are associated with subnets.</p><p>Each subnet must be associated with a NACL.</p><p>A NACL contains inbound and outbound rules that determine which traffic is permitted to cross the subnet.</p><h3>NACLs Are Stateless</h3><p>This is the biggest difference between Security Groups and NACLs.</p><p>A stateless firewall doesn’t automatically remember return traffic as part of an established connection.</p><p>Instead, inbound and outbound traffic are evaluated independently.</p><p>Let’s return to our EC2 web server.</p><p>Customer sends an HTTPS request to the server on TCP port 443.</p><p>The inbound NACL rules permit the request.</p><p>But when the server responds, the outbound traffic must also be permitted by the NACL.</p><p>The response generally travels to an ephemeral port on the client’s system.</p><p>If the outbound NACL rules block that traffic, the connection may fail.</p><p>Even though the original inbound request was allowed.</p><p>This is why understanding <strong>ephemeral ports</strong> is important when configuring restrictive NACLs.</p><h3>NACLs Support Allow and Deny Rules</h3><p>Unlike Security Groups, NACLs can explicitly allow or deny traffic.</p><p>For example, you might create a rule that denies traffic from a particular IP address range.</p><p>This makes NACLs useful when you need subnet-level filtering or explicit network denies.</p><h3>NACL Rules Are Evaluated in Numerical Order</h3><p>Each NACL rule has a number.</p><p>AWS evaluates matching rules starting with the lowest rule number.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6BD_Jc0mNI6u_JD8Zc2Fow.png" /></figure><p>If traffic originates from the example subnet 203.0.113.0/24 rule 100 matches first and denies it.</p><p>AWS does not continue to rule 200.</p><p>The * rule is the implicit final deny rule for traffic that doesn&#39;t match any earlier rule.</p><p><strong>Rule order matters.</strong></p><p>The default NACL created with a VPC allows all inbound and outbound traffic. A newly created custom NACL initially denies traffic until you configure appropriate rules</p><h3>Security Groups vs NACLs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KWatj38VBT8F5qMT_I04Cg.png" /></figure><p>The easisest way to remember is.</p><p>Security Groups - Stateful resource level firewall</p><p>NACL - Stateless subnet level firewall.</p><h3>Inbound, Outbound and Ephemeral Ports</h3><p>A customer opens a browser and visits your website.</p><p>The browser establishes a connection to your EC2 server on TCP port 443.</p><p>But, the customer’s device also uses a temporary source port, known as an <strong>ephemeral port</strong>.</p><p>For example, the connection might look like this.</p><p>Customer &gt; EC2</p><p>Client 49152 &gt; Server 443</p><p>When the server responds, the direction is reversed</p><p><strong>EC2 &gt; Customer</strong></p><p>Server 443 &gt; Client 49152</p><p>The client’s ephemeral port (49152) is where the response is directed.</p><p>A Security Group tracks the authorized connection and allows the response.</p><p>A NACL evaluates the returning traffic independently.</p><p>Therefore, if you’re using restrictive custom NACL rules, you need to consider for the ephemeral port ranges.</p><p>The appropriate ranges depend on the client operating systems and other components involved in the connection.</p><p>This is one of the reasons NACL misconfigurations can create connectivity problems.</p><h3>Real World Example Why I cant Access My EC2 Website</h3><p>Okay you deployed an EC2 instance running Nginx inside a public subnet.</p><p>Your VPC has an internet gateway, the subnet has the appropriate route, and your EC2 instance has a public IP address.</p><p>You also configured a Security Group that allows inbound HTTP traffic on TCP port 80.</p><p>Everything looks correct.</p><p>But when you try to access the website, the connection fails.</p><p>What’s wrong?</p><p>One possible explanation is a restrictive custom NACL.</p><p>Imagine its inbound rules allow HTTP requests on port 80, but its outbound rules don’t allow the response traffic destined for the client’s ephemeral port.</p><p>The request can enter the subnet, but the response can’t leave.</p><p>The Security Group is not the problem.</p><p>The subnet’s NACL is preventing the communication.</p><p>To troubleshoot, you would examine</p><ol><li>The EC2 instance’s Security Group rules.</li><li>The subnet’s inbound and outbound NACL rules.</li><li>The route table and internet gateway configuration.</li><li>The instance’s public IP configuration</li><li>The operating system firewall and whether Nginx is running.</li><li>Network diagnostic information, such as VPC Flow Logs, where available.</li></ol><p>A correctly configured Security Group does not guarantee connectivity if another network control blocks the traffic.</p><h3>Why Does AWS Provide Both</h3><p>If Security Groups already protect our resources, why would we need NACLs</p><p>Because they operate at different levels.</p><p>Security Groups are generally for controlling access to individual resources.</p><p>For example, you might allow your application server to communicate with a database on TCP port 5432 while denying unrelated connections.</p><p>NACLs provide another layer of filtering at subnet boundaries.</p><p>For example, an organization might use a NACL to deny traffic from a particular IP range across an entire subnet.</p><p>This is an example of defense in depth.</p><p>Instead of relying on one control, you use multiple security measures.</p><p>But, additional controls should be configured carefully. An overly complicated NACL can create operational problems without necessarily improving security.</p><p>Security Groups or NACLs dont replace application security, identity management, encryption, or monitoring.</p><h3>Security Best Practices</h3><p>When designing AWS network security, keep these in mind.</p><p><strong>Apply the Principle of Least Privilege.</strong></p><p>Only allow the network traffic your application actually requires.</p><p><strong>Restrict Administrative Access.</strong></p><p>Avoid exposing SSH or RDP to the entire internet unless there’s a specific reasonj.</p><p><strong>Use Security Group References Where Appropriate.</strong></p><p>Instead of allowing a database connection from an entire IP range, you can often the Security Group associated with the application that needs access.</p><p><strong>Monitor and Troubleshoot.</strong></p><p>Use tools such as VPC Flow Logs and other AWS monitoring capabilities to investigate network connectivity and suspicious activity.</p><h3>Final Thoughts</h3><p>In our previous lesson, we learned how Amazon VPC gives us control over our cloud network.</p><p>Now we’ve explored two mechanisms that help secure communication within that network.</p><p>Security Groups provide stateful firewall associated with individual resources.</p><p>Network ACLs provide stateless firewall at the subnet level.</p><p>Both play a role in controlling network traffic, but serve different purposes.</p><p>And that’s why understanding the fundamentals matters.</p><p>When you’re troubleshooting a connection failure, designing a secure cloud architecture, or preparing for an AWS certification, knowing the difference between stateful and stateless filtering helps you reason through what the network is actually doing.</p><h3>Feel free to connect with me on Social Media and Say Hi</h3><p>Instagram</p><p><a href="https://www.instagram.com/naruto_mma">https://www.instagram.com/naruto_mma</a>/</p><p>X</p><p><a href="https://x.com/Incitelabz">Curtis (@Incitelabz) on X</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfb227b44605" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Amazon VPC Explained - Simply Understanding your Private Network in AWS]]></title>
            <link>https://medium.com/@incit3me/amazon-vpc-explained-simply-understanding-your-private-network-in-aws-41c117f26340?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/41c117f26340</guid>
            <category><![CDATA[amazon-web-services]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[amazon-vpc]]></category>
            <category><![CDATA[cloud-networking]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Mon, 19 Oct 2026 02:57:53 GMT</pubDate>
            <atom:updated>2026-10-19T02:57:53.837Z</atom:updated>
            <content:encoded><![CDATA[<p>How subnets, routing, and network security work together to build secure cloud environments</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oE4kc60nyA4G3omIYuO1YA.jpeg" /></figure><h3>Introduction</h3><p>Imagine you are building a house.</p><p>You have your rooms, doors, and your security system. Before you can organize everything inside, you need property where the house will be.</p><p>Cloud Computing works similiary but they differ</p><p>We talked about EC2, which we know provides virtual servers, and services like Amazon EBS and EFS provide storage</p><p>The important questions is where do these servers live, and how do we control and communicate with them</p><p>This is exactly what Amazon Virtual Private Cloud (VPC) does</p><p>It allows you to create a logically isolated virtual network inside AWS, where you can launch resources, organize your network, and control how traffic flows.</p><p>Lets talk about it.</p><h3>What is Amazon VPC</h3><p>You can think of Amazon VPC as your own private neighborhood inside AWS</p><p>AWS provides the infrastructure and tools, but you design the network to your specific needs.</p><p>You decide what goes in like:</p><ul><li>What IP address ranges your network uses.</li><li>How your network is divided into subnets.</li><li>Which resources can communicate with the internet.</li><li>How traffic moves between networks.</li><li>What network security controls protect your resources.</li></ul><p>Example, imagine you’re building a website with an application server and a database.</p><p>You may want customers to reach the website without allowing them to connect directly to your database.</p><p>A VPC gives you the network infrastructure to design that separation.</p><p>Simply put: A VPC is your private network environment in the AWS Cloud.</p><h3>What are Subnets</h3><p>Imagine your neighborhood has different sections.</p><p>Some areas are open to visitors, while others are restricted to residents and authorized individuals</p><p>Subnets work in a similar way but just in a computer sense</p><p>A subnet is a range of IP addresses within your VPC. Each subnet exists in one Availability Zone.</p><p>We commonly design subnets as either public or private.</p><h3>Public Subnet</h3><p>A public subnet has a route to an Internet Gateway (IGW).</p><p>Resources inside it can communicate directly with the internet when they also have the public addressing and security permissions.</p><p>Examples include</p><ul><li>Public facing load balancers</li><li>Bastion hosts</li><li>Internet facing application that need internet access</li></ul><h3>Private Subnet</h3><p>A private subnet does not have a direct route to an Internet Gateway pretty much. Easier way to understand is that your subnet is not connected to an Internet Gateway.</p><p>It’s usually used for resources that should not be directly reachable from the internet.</p><p>Examples include:</p><ul><li>Internal application servers</li><li>Databases</li><li>Backend services</li></ul><p>The key idea is that not every resource in your cloud environment needs to be exposed to the internet.</p><h3>So What is an Internet Gateway</h3><p>An Internet Gateway is just a connection between your private neighborhood and the outside world.</p><p>An Internet Gateway is what allows communication between your VPC and the internet with out it your EC2 or other resources would not have internet access.</p><p>Most importantly attaching one to your VPC does notautomatically make every resource publicly accessible.</p><p>You still need the correct routing, public IP configuration, and security rules.</p><p>For example, an EC2 instance in a public subnet may use an Internet Gateway to communicate with internet users.</p><p>But a database in a private subnet should not have an Internet Gateway connection and must remain inaccessible directly from the public internet.</p><h3>What is NAT Gateway</h3><p>Here’s where things get fun.</p><p>What happens your server in a private subnet needs to download software updates or access an external service?</p><p>You don’t want to give that server a public IP address.</p><p>That’s where a NAT Gateway can help.</p><p>A public NAT Gateway allows resources in private subnets to initiate outbound connections outside the VPC, like the internet, while preventing unsolicited inbound connections from the internet through that gateway.</p><p>You can think of it like a building where employees can contact outside businesses, but outsiders cannot directly call into every private office.</p><p><strong>Internet Gateway</strong> Supports direct internet connectivity for public resources.</p><p><strong>NAT Gateway</strong> Allows private resources to initiate outbound connections without exposing them to the internet.</p><h3>What Are Route Tables</h3><p>So your driving through a city without road signs.</p><p>You dont know which road leads to your destination.</p><p>AWS route tables solve a similar problem.</p><p>A route table has rules that determine where network traffic should be directed. Think of someone directing traffic.</p><p>For example</p><ul><li>Traffic destined for another IP address inside your VPC can use the local route.</li><li>Traffic from a public subnet to the internet can be directed toward an Internet Gateway.</li><li>Internet traffic bound from a private subnet can be directed toward a NAT Gateway.</li></ul><p>Route tables are essential because they determine where traffic goes.</p><p>Security controls determine whether that traffic is allowed.</p><h3>Security Groups vs Network ACLs</h3><p>Lets talk about the security my favorite part</p><p>AWS provides a variety of ways to control your network traffic inside a VPC.</p><p>The most important tools are Security Groups and Network Access Control Lists (NACLs).</p><h3>Security Groups</h3><p>Security Group is just a security guard protecting a particular resource.</p><p>Security Groups control allowed inbound and outbound traffic for resources like EC2 instances.</p><p>They are</p><ul><li>Stateful</li><li>Allow rule based</li><li>Associated with network interfaces</li></ul><p>Stateful just means that when traffic is allowed in one direction, the corresponding response traffic is automatically allowed because it has to remember that connection.</p><h3>Network ACLs</h3><p>Think of a Network ACL as a security checkpoint at the entrance to a neighborhood section.</p><p>NACLs operate at the subnet level.</p><p>They are</p><ul><li>Stateless</li><li>Able to use allow and deny rules</li><li>Evaluated in numbered rule order</li></ul><p>Stateless means return traffic must be allowed separately.</p><p>Security Group protects the resource at the network interface level<strong>.</strong></p><p>Network ACL protects at the subnet boundary<strong>.</strong></p><p>Both are essential for security of your VPC.</p><h3>Real World Example Building a Secure Website</h3><p>Now we can put everything together</p><p>okay so you are designing a web application in AWS.</p><p>You create a VPC with two public subnets and two private subnets across two Availability Zones.</p><p>Your architectur looks like this totally up to you</p><p><strong>Internet. Internet Gateway. Public Application Load Balancer. Private EC2 Application Servers. Private Database</strong></p><p>Here is how this works</p><ol><li>A customer visits your website.</li><li>The customers request reaches the public facing Application Load Balancer.</li><li>Your load balancer forwards traffic to your application servers in private subnets.</li><li>The request reaches the public facing Application Load Balancer.</li><li>Security Groups restrict which resources can communicate with each other</li></ol><p>If the your private application servers need outbound internet access, you can use NAT Gateway.</p><p>This design helps reduce unnecessary public exposure and supports availability across multiple Availability Zones.</p><h3>Why VPC are Important for Cloud Security</h3><p>As I continue studying AWS security and working through hands on labs, thing are becoming increasingly clear</p><p>You can not secure an environment you dont understandand.</p><p>VPC networking is fundamental to that understanding.</p><p>A secure design requires you to ask.</p><ul><li>Should this resource be publicly accessible</li><li>Which systems actually need to communicate</li><li>Are we allowing more traffic than necessary</li><li>How can we monitor network activity</li><li>What happens if one component becomes compromised</li></ul><p>Services such as VPC Flow Logs can help capture information about IP traffic to and from network interfaces, supporting troubleshooting and security investigations.</p><p>This is where networking and cybersecurity start coming together.</p><h3>Final Thoughts</h3><p>Amazon VPC is more than where you just keep your EC2.</p><p>Its the networking foundation that helps you design how your recoures communicate in the cloud.</p><p>If you can remember these you should be good</p><ul><li>VPC is your private neighborhood</li><li>Subnets are sections within your neighborhood</li><li>Route Tables are Directions for network traffic</li><li>Internet Gateway is your connection to the Internet</li><li>NAT Gateway is your outbound access for private resources</li><li>Security Groups Resource based protection that work on the instance level</li><li>Network ACLs protect at the subnet level</li></ul><h3>Feel free to connect with me on Social media and say HI</h3><p>Instagram</p><p><a href="https://www.instagram.com/naruto_mma">https://www.instagram.com/naruto_mma</a>/</p><p>X</p><p><a href="https://x.com/Incitelabz">Curtis (@Incitelabz) on X</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41c117f26340" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Passed the AWS Solutions Architect Associate And Learned to Think Like an Architect]]></title>
            <link>https://medium.com/@incit3me/how-i-passed-the-aws-solutions-architect-associate-and-learned-to-think-like-an-architect-12e6505937fe?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/12e6505937fe</guid>
            <category><![CDATA[aws-solutions-architect]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Wed, 02 Sep 2026 23:00:40 GMT</pubDate>
            <atom:updated>2026-09-02T23:00:40.246Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/264/1*xqsbawR4KX-dtEO4S_BPJg.png" /></figure><p>“ <strong>You don’t have to see yourself as an architect before you begin. You develop that way of thinking through the work</strong>. “</p><h4><strong>I almost convinced myself cloud wasn’t for me. I’m grateful I didn’t listen. Here’s the study process that changed how I understand AWS and what I learned along the way</strong></h4><p>When I first considered pursuing cloud computing, I was hesitant.</p><p>Cloud seemed distant something I could always learn later.</p><p>I also heard plenty of opinions about whether cloud was worth pursuing. It would have been easy to listen to the noise and convince myself that I didn’t need to go down this path.</p><p>I’m so grateful I didn’t.</p><p>Considering where I came from, sometimes I still stop and think about the fact that I’m actually learning cloud architecture, cybersecurity, and AI.</p><p>There was a time when I couldn’t imagine myself doing this.</p><p>And when I first saw the words <strong>AWS Solutions Architect</strong>, I’ll admit that the title itself was intimidating.</p><p><em>Me an Architect?</em></p><p>We don’t always see ourselves that way.</p><p>The idea that I could design systems and architect solutions on AWS sounded like something far away from where I was.</p><p>But I eventually learned something.</p><p><strong>You don’t have to see yourself as an architect before you begin.</strong></p><p>You develop that way of thinking through the work.</p><p>And that’s exactly what happened to me.</p><h4><strong>I Started With the Fundamentals</strong></h4><p>I didn’t begin my AWS journey with Solutions Architect.</p><p>I started with the <strong>AWS Certified Cloud Practitioner</strong>.</p><p>That was intentional.</p><p>I strongly believe in fundamentals.</p><p>I approached cybersecurity similarly. I earned my CompTIA A+ and Security+ because I’ve always believed</p><p><strong><em>You can’t secure what you don’t understand.</em></strong></p><p>So when I studied for Cloud Practitioner, I didn’t want to do the bare minimum just to pass an exam.</p><p>I took my time.</p><p>Studied the services.</p><p>Took extensive notes.</p><p>Drew diagrams.</p><p>Read additional material to reinforce what I was learning.</p><p>Worked through use cases.</p><p>I even started getting hands on with AWS.</p><p>After passing Cloud Practitioner, I pursued the <strong>AWS Certified AI Practitioner</strong> because I believe cloud computing and artificial intelligence are going to become increasingly interconnected.</p><p>I repeated much of the same learning process there.</p><p>Looking back, taking Cloud Practitioner seriously was one of the best things I could have done before Solutions Architect.</p><p>It gave me a foundation.</p><p>Could someone skip it and go directly to SAA?</p><p>Sure.</p><p>But my goal wasn’t to find the shortest possible route.</p><p><strong>I wanted to understand AWS.</strong></p><h4>Don’t Just Memorize AWS Services</h4><p>This became one of the biggest lessons of my entire SAA journey.</p><p>When you’re beginning AWS, it’s easy to see a giant list of services.</p><p>EC2.</p><p>S3.</p><p>RDS.</p><p>Route 53.</p><p>CloudFront.</p><p>ELB.</p><p>Auto Scaling.</p><p>SQS.</p><p>EFS.</p><p>IAM.</p><p>And you can easily fall into the trap of trying to memorize what each one does.</p><p>But memorizing a definition isn’t the same as understanding architecture.</p><p>I wanted to understand AWS intuitively.</p><p><strong>What problem does this service solve?</strong></p><p><strong>Why was it created?</strong></p><p><strong>When would I choose it?</strong></p><p><strong>What other AWS services does it work with?</strong></p><p>That last question became especially important.</p><p>At first, I struggled to understand which services were compatible and how everything connected.</p><p>Eventually, I realized</p><p><strong><em>AWS services weren’t designed to exist in isolation.</em></strong></p><p>They work together.</p><p>Once I stopped viewing AWS as dozens of disconnected services and started seeing it as an ecosystem, things began clicking.</p><h4>Drawing Architectures Changed Everything</h4><p>For my SAA preparation, I used <strong>Stéphane’s Udemy course</strong> and actually followed along with the hands on portions.</p><p>But one of the most valuable things I did was something incredibly simple</p><p><strong>I drew the architectures myself.</strong></p><p>Not just looking at someone else’s diagram.</p><p>Actually putting pen to paper and figuring out</p><p><em>Where does this service go?</em></p><p><em>What connects to what?</em></p><p><em>Why is the load balancer here?</em></p><p><em>Where does Auto Scaling fit?</em></p><p><em>Where is the database?</em></p><p><em>What happens if this component fails?</em></p><p>Drawing forced me to think differently.</p><p>When you’re watching someone else explain an architecture, it can feel obvious.</p><p>But close the video and try drawing it yourself.</p><p>Now your brain has to reconstruct the architecture.</p><p>That is different.</p><p>That’s where I started feeling like I wasn’t simply studying AWS services anymore.</p><p><strong>I was beginning to think like an architect.</strong></p><h4>My Note-Taking Process Wasn’t Exciting But It Worked</h4><p>Ill warn you</p><p>My study process isn’t glamorous.</p><p>I took extensive notes <strong>by hand</strong>.</p><p>I believe there is something powerful about putting pen to paper. Writing something yourself forces you to process what you’re learning instead of passively watching someone else explain it.</p><p>Then I took those handwritten notes and transferred them into a Google Doc.</p><p>That meant I was processing the information again.</p><p>Then I reread them.</p><p>If there were services or concepts I still didn’t completely understand, I used AI to help clarify them and explore scenarios until they made sense.</p><p>It was repetitive.</p><p>Sometimes very boring.</p><p>But that’s the point.</p><p>I wasn’t optimizing for</p><p><strong>“How quickly can I pass?”</strong></p><p>I was optimizing for:</p><p><strong>“How deeply can I understand this?”</strong></p><p>Because shortcuts may help you remember something long enough to answer a question.</p><p>Understanding stays with you much longer.</p><h4>How I Used Practice Exams</h4><p>Practice exams were another important part of my preparation, but I didn’t use them simply to chase higher scores.</p><p>If I got something wrong, I wanted to know <strong>why</strong>.</p><p>Why was my answer wrong?</p><p>Why was the correct answer better?</p><p>What architectural requirement in the scenario should have pointed me toward the correct service?</p><p>But I also did something that I think is overlooked</p><p><strong>I reviewed questions I got right.</strong></p><p>Sometimes you can get a question correct for the wrong reason.</p><p>Maybe you guessed.</p><p>Maybe you eliminated two answers and got lucky.</p><p>Maybe you remembered a phrase without actually understanding the architecture.</p><p>I didn’t want that.</p><p>I wanted to understand <strong>why the answer was correct</strong> before moving on.</p><p>That takes longer.</p><p>But again, I wasn’t interested in shortcuts</p><h4>The Moment AWS Started Clicking</h4><p>I started asking</p><p><strong>“What problem am I trying to solve?”</strong></p><p>That changed everything.</p><p>Need resilience</p><p>Storage</p><p>Disaster recovery</p><p>Security</p><p>Serverless</p><p>Multi-AZ</p><p>Scalability</p><p>Compliance</p><p>Now I could work backward from the architectural requirement.</p><p>The services became <strong>tools for solving problems</strong>, rather than definitions on flashcards.</p><p>That’s when AWS really started making sense to me</p><h4>My Final Days Before the Exam</h4><p>During the final days, I didn’t suddenly try to cram everything into my brain.</p><p>At some point, you have to trust the work you’ve already done.</p><p>I continued reviewing practice tests.</p><p>I went through scenarios and different AWS use cases.</p><p>I used AI to challenge my understanding.</p><p>I did hands on work.</p><p>And I focused particularly on areas where I still felt uncertain.</p><p>Strangely enough, this became one of my favorite parts of studying.</p><p>I wasn’t trying to memorize AWS anymore.</p><p>I was thinking about <strong>real world application</strong>.</p><p>And that’s where I believe some of the deepest learning happens.</p><h4>What the SAA Exam Taught Me</h4><p>I was nervous taking the exam.</p><p>But while I was reading the questions, I kept bringing myself back to something simple</p><p><strong><em>What problem is this question asking me to solve?</em></strong></p><p>Is this a disaster-recovery problem?</p><p>Storage?</p><p>Compliance?</p><p>Serverless?</p><p>Multi-AZ?</p><p>Security?</p><p>Resilience?</p><p>Once I identified the underlying problem, I could start thinking about which architecture made sense.</p><p>That’s an important distinction for anyone preparing for SAA.</p><p>From my experience, the exam wasn’t simply asking</p><p><strong>“What is this AWS service?”</strong></p><p>It was heavily scenario based.</p><p>You need to understand what the services do well enough to determine how they solve an architectural problem.</p><p>That’s another reason I’m grateful I spent so much time on fundamentals.</p><h4>Then I Passed</h4><p>Passing the AWS Solutions Architect Associate meant more to me than adding another certification to my resume.</p><p>Something had changed.</p><p>The title that once intimidated me didn’t feel so distant anymore.</p><p>I had spent enough time studying architectures, drawing them, understanding services, working through scenarios and getting hands on that my way of thinking had changed.</p><p>I could look at AWS and start seeing <strong>systems</strong> rather than individual services.</p><p>I could think about how those systems might help an organization solve an actual problem.</p><p>For the first time, I really felt like I was becoming part of the AWS world.</p><p>And I realized</p><p><strong>I can actually do this.</strong></p><p>Considering where I started, that realization means a lot to me.</p><h4>If I Could Start Over</h4><p>If I went through SAA preparation again, there are two things I would do even more of:</p><p><strong>Draw more architectures.</strong></p><p><strong>Get even more hands on.</strong></p><p>Those were some of the most valuable parts of my preparation.</p><p>I’m also grateful that I didn’t rush past Cloud Practitioner.</p><p>For me, the fundamentals mattered.</p><p>They gave everything else somewhere to connect.</p><h4>Solutions Architect Wasn’t the Finish Line</h4><p>Today, I’m studying for the <strong>AWS Security Specialty</strong>.</p><p>And SAA has already been incredibly valuable.</p><p>Because now the question has changed.</p><p>Before, I was asking</p><p><strong>How do I architect this system?</strong></p><p>Now I’m asking</p><p><strong>How do I secure this architecture?</strong></p><p>I’m working through hands on AWS security labs involving IAM, CloudTrail, incident identification, remediation, and other security concepts.</p><p>And once again, the architecture foundation matters.</p><p>You can’t properly secure something if you don’t understand how it’s built.</p><p>That’s why the progression makes sense to me</p><p><strong>Understand the cloud, Architect the cloud, Secure the cloud.</strong></p><h4>And I’m Not Stopping With AWS</h4><p>My next major step is <strong>Microsoft Azure</strong>.</p><p>I want to become multi cloud.</p><p>And I’m going to approach Azure exactly how I approached AWS</p><p>Start with the fundamentals.</p><p>Understand the services.</p><p>Get hands on.</p><p>Draw the architectures.</p><p>Understand the problems each service solves.</p><p>Then go deeper.</p><p>The difference is that this time I’m not starting from zero.</p><p>AWS taught me how to <strong>think about cloud architecture</strong>.</p><p>Now I get to take those mental models into another cloud ecosystem and discover what’s similar, what’s different, and how the pieces translate.</p><p>Eventually, I want my journey to bring together the areas I’ve become passionate about</p><p><strong>Cloud.</strong></p><p><strong>Cybersecurity.</strong></p><p><strong>Artificial intelligence.</strong></p><p>Imagine securing multi cloud environments while AI agents increasingly operate inside those environments.</p><p>That’s the direction I’m moving toward.</p><p>And sometimes I still can’t believe I’m actually doing it.</p><h4>I’m Grateful I Started</h4><p>If there’s one thing I want someone reading this to take away, it isn’t that you need to study exactly the way I did.</p><p>It’s this</p><p><strong>Don’t disqualify yourself before you’ve even started.</strong></p><p>There was a point when “AWS Solutions Architect” sounded intimidating to me.</p><p>Cloud seemed distant.</p><p>I could have listened to other people’s opinions.</p><p>I could have told myself I’d learn it someday.</p><p>I could have assumed this world wasn’t meant for someone from where I came from.</p><p>I’m grateful I didn’t.</p><p>I started at the bottom.</p><p>I learned the fundamentals.</p><p>I took notes.</p><p>I drew diagrams.</p><p>I got things wrong.</p><p>I went back and figured out why.</p><p>I kept learning.</p><p>And eventually, something that once seemed intimidating became something I could understand.</p><p>Then something I could build.</p><p>And now something I’m learning to secure.</p><p><strong>You don’t have to know how far the journey will take you before you begin.</strong></p><p>Sometimes you just have to take the first step.</p><p>For me, that first step was AWS Cloud Practitioner.</p><p>Today, I’m an <strong>AWS Certified Solutions Architect Associate</strong>, studying AWS security and preparing to expand into multi-cloud.</p><p>And I’m just getting started.</p><h4>Follow me On Social Media and Say Hi</h4><p>Instagram</p><p><a href="https://www.instagram.com/naruto_mma">https://www.instagram.com/naruto_mma</a>/</p><p>X</p><p><a href="https://x.com/Incitelabz">Curtis (@Incitelabz) on X</a></p><p>YouTube</p><p><a href="https://www.youtube.com/@Incit3me"></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12e6505937fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Explained Simply Amazon EFS — The Shared Drive for Your EC2 Servers]]></title>
            <link>https://medium.com/@incit3me/aws-explained-simply-amazon-efs-the-shared-drive-for-your-ec2-servers-e93dc3e64448?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e93dc3e64448</guid>
            <category><![CDATA[amazon-web-services]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Thu, 27 Aug 2026 15:01:02 GMT</pubDate>
            <atom:updated>2026-08-27T15:01:02.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*sVLW0PD-zFFkijAeeqPoeQ.png" /></figure><p>AWS has multiple storage services, but they aren’t all solving the same problem.</p><p>You may already know about <strong>Amazon EBS</strong>, which provides block storage that can be attached to an EC2 instance.</p><p>You may also know about <strong>Amazon S3</strong>, which stores data as objects inside buckets.</p><p>But what happens when <strong>multiple EC2 instances need access to the same files at the same time?</strong></p><p>That’s where <strong>Amazon Elastic File System (EFS)</strong> comes in.</p><h3>What is Amazon EFS?</h3><p>The easiest way I think about it is</p><p><strong><em>EFS is like a shared network drive for your EC2 instances.</em></strong></p><p>Imagine an office with ten employees.</p><p>Instead of every employee keeping a separate copy of the same files on their individual computers, the company creates one shared network folder.</p><p>Everyone who has permission can connect to that folder and work with the same files.</p><p>EFS brings that idea to AWS.</p><p>Multiple EC2 instances can connect to the same EFS file system and read or write files simultaneously.</p><h3>Let’s Make It Even Simpler</h3><p>Imagine you’re working on a document with ten people.</p><h3>EBS is like having the document on your own computer.</h3><p>The file is sitting on your drive.</p><p>You can work with it, but everyone else doesn’t automatically have access to that same local drive.</p><h3>EFS is like a shared Google Doc</h3><p>Now all ten people can open the same document.</p><p>Someone makes a change.</p><p>Everyone else can see it.</p><p>Another person adds something.</p><p>Everyone is still working from the same central document.</p><p>That’s essentially the idea behind EFS.</p><h3>Why Would Multiple EC2 Instances Need the Same Files?</h3><p>This becomes especially useful when we start thinking about <strong>scalable applications</strong>.</p><p>Imagine you have a website running on several EC2 instances.</p><p>A load balancer distributes users across those servers.</p><p>Now imagine a user uploads an image.</p><p>If that image exists only on the local storage of <strong>EC2-A</strong>, what happens when another request gets routed to <strong>EC2-B</strong>?</p><p>EC2-B may not have that file.</p><p>Instead, the servers can use a shared EFS file system.</p><p>Now</p><p><strong>EC2-A can share with EFS</strong></p><p><strong>EC2-B can share with EFS</strong></p><p><strong>EC2-C can share with EFS</strong></p><p>All of them can access the same shared files.</p><p>This is one reason EFS can be useful for websites, content-management platforms such as WordPress, and applications that need access to common datasets.</p><h3>Elastic Is Right in the Name</h3><p>One of my favorite things about AWS is how often the name tells you something about the service.</p><p>It’s called</p><p><strong>Elastic File System</strong></p><p>because you don’t have to constantly manage the underlying storage capacity yourself.</p><p>As files are added or removed, the file system can automatically grow or shrink accordingly.</p><p>That’s part of the larger cloud computing idea of <strong>elasticity</strong>.</p><p>Instead of purchasing a physical file server and trying to predict how much storage you’ll need years into the future, cloud resources can adjust as your requirements change.</p><h3>EFS vs. EBS vs. S3</h3><p>EBS is just a hard drive attached to a server</p><p>Your EC2 instance needs block storage.</p><p>S3 is just a massive object storage system</p><p>You need somewhere to store objects such as</p><ul><li>Images</li><li>Videos</li><li>Backups</li><li>Documents</li><li>Logs</li><li>Static files</li></ul><p>EFS is just a shared network folder</p><p>Multiple servers need access to a common file system.</p><h3>AWS Handles the Infrastructure</h3><p>Another benefit of EFS is that AWS manages the underlying storage infrastructure.</p><p>You don’t have to maintain physical storage hardware yourself.</p><p>That fits one of the ideas that attracted me to cloud computing in the first place:</p><p><strong>Spend more time building applications and less time maintaining physical infrastructure.</strong></p><p>Your servers simply need access to the file system.</p><p>AWS handles the backend.</p><h3>Final Thoughts</h3><p>Amazon EFS solves a simple but important problem</p><p><strong><em>How can multiple servers work with the same files?</em></strong></p><p>Give them a shared file system.</p><p>That’s EFS.</p><p>And as applications scale across multiple EC2 instances, understanding shared storage becomes increasingly important.</p><p>You don’t necessarily need to remember every EFS feature when you’re first learning AWS.</p><p>Start with the fundamental idea</p><p><strong>EBS gives a server a drive.</strong></p><p><strong>EFS gives multiple servers a shared file system.</strong></p><p><strong>S3 gives applications scalable object storage.</strong></p><p>Once that foundation makes sense, the deeper architecture becomes much easier to understand.</p><h3>Follow me on Social Media and say HI</h3><p>Instagram</p><p><a href="https://www.instagram.com/naruto_mma">https://www.instagram.com/naruto_mma</a>/</p><p>X</p><p><a href="https://x.com/Incitelabz">Curtis (@Incitelabz) on X</a></p><p>YouTube</p><p><a href="https://www.youtube.com/@Incit3me"></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e93dc3e64448" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Explained Simply Understanding AWS IAM]]></title>
            <link>https://medium.com/@incit3me/aws-explained-simply-understanding-aws-iam-14582dc958e9?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/14582dc958e9</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-solutions-architect]]></category>
            <category><![CDATA[aws-iam]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Wed, 12 Aug 2026 18:42:55 GMT</pubDate>
            <atom:updated>2026-08-12T18:42:55.170Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*LfEwB6CN2Syki9UtHaETbg.png" /></figure><h3><strong>Your Cloud’s Security Guard</strong></h3><p>When most people think about cloud security, they picture firewalls, encryption, or hackers trying to break into systems.</p><p>But before any of that matters, you have to answer one simple question</p><p><strong>Who should be allowed inside?</strong></p><p>That’s exactly what <strong>AWS Identity and Access Management (IAM)</strong> is designed to solve.</p><p>Think of IAM as the <strong>security guard for your AWS account</strong>. Every time someone or something tries to access your cloud resources, IAM decides whether they’re allowed in and what they’re allowed to do.</p><h3>Imagine a Corporate Office</h3><p>The easiest way I think about IAM is by imagining a large corporate office.</p><p>Every day, employees, contractors, and visitors arrive at the building.</p><p>Not everyone should have the same level of access.</p><p>An HR employee doesn’t need access to the server room.</p><p>A visitor fixing the printer doesn’t need permanent access to company files.</p><p>The same principle applies to AWS.</p><p>IAM controls <strong>who can sign in and what they can use</strong></p><h3>The Four Building Blocks of IAM</h3><h3>Users</h3><p>Users represent individual people or applications that need access to AWS.</p><p>Think of a user as an employee receiving their own company ID badge.</p><p>Each badge identifies one specific person and allows them to sign in using their own credentials.</p><p>Every employee should have <strong>their own badge</strong> not a shared one.</p><h3>Groups</h3><p>Imagine a company with fifty accountants.</p><p>Instead of giving each accountant permissions one at a time, you place them into the <strong>Accounting Department</strong>.</p><p>Now every accountant automatically receives the same access.</p><p>That’s exactly what IAM Groups do.</p><p>Groups allow multiple users with similar responsibilities to share the same permissions, making administration much easier</p><h3>Roles</h3><p>Roles are one of my favorite IAM features.</p><p>Imagine a technician arrives to repair the office printer.</p><p>You wouldn’t hire them as a full-time employee just to give them access for one afternoon.</p><p>Instead, you hand them a <strong>temporary visitor badge</strong> that expires when they’re finished.</p><p>IAM Roles work the same way.</p><p>They provide <strong>temporary credentials</strong> that can be assumed by users, applications, or AWS services when they’re needed.</p><p>For example, an EC2 instance might temporarily assume a role to securely access an S3 bucket without storing permanent credentials.</p><h3>Policies</h3><p>Policies are the written rules that define what is allowed or denied.</p><p>Think of them as the company’s employee handbook.</p><p>It explains which rooms each department can enter and which areas remain off limits.</p><p>In AWS, policies define what actions identities can perform on specific resources</p><h3>The Principle of Least Privilege</h3><p>One of the most important security concepts you’ll encounter is the <strong>Principle of Least Privilege (PoLP).</strong></p><p>Simply put</p><p><strong>Give users only the permissions they need to perform their jobs nothing more.</strong></p><p>If someone only needs to download files from an S3 bucket, don’t give them full administrative access.</p><p>Limiting permissions reduces the potential damage if an account is compromised or a mistake is made.</p><p>This principle is one of the foundations of cloud security and appears throughout AWS.</p><h3>Understanding Default Deny</h3><p>Imagine walking into a secure office building without an employee badge.</p><p>You walk up to the front desk and ask to enter.</p><p>The security guard doesn’t ask &quot;Why<em> shouldn’t I let you in?”</em></p><p>Instead, they ask: &quot;Can<strong><em> you prove you’re allowed to enter?”</em></strong></p><p>If your name isn’t on the approved access list, you’re denied entry.</p><p>AWS IAM works the same way.</p><p>Every request starts with <strong>no permissions</strong>.</p><p>Access is granted only when a policy explicitly allows it.</p><p>In other words</p><p><strong>No permission means no access.</strong></p><p>That default deny model is one of the reasons IAM is such a powerful security service.</p><h3>My Biggest Takeaway</h3><p>Before studying AWS, I thought IAM was simply about creating users and passwords.</p><p>Now I see it differently.</p><p>IAM is the foundation of cloud security.</p><p>Every EC2 instance, S3 bucket, Lambda function, and database depends on making sure the <strong>right identities have the right permissions at the right time</strong>.</p><p>Without proper identity management, even the strongest infrastructure can become vulnerable.</p><h3>Final Thoughts</h3><p>AWS is built on a shared responsibility model, and one of the most important responsibilities customers have is controlling access to their cloud resources.</p><p>The better you understand IAM, the stronger every AWS architecture you build will become.</p><p>Sometimes the most important security feature isn’t adding more protection.</p><p>It’s making sure only the right people can get through the front door</p><h3>Follow me on the Socials and say Hi</h3><p>Instagram</p><p><a href="https://www.instagram.com/naruto_mma">https://www.instagram.com/naruto_mma</a>/</p><p>X</p><p><a href="https://x.com/Incitelabz">Curtis (@Incitelabz) on X</a></p><p>YouTube</p><p><a href="https://www.youtube.com/@Incit3me"></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14582dc958e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Explained Simply Amazon S3]]></title>
            <link>https://medium.com/@incit3me/aws-explained-simply-amazon-s3-3a8c378b35cc?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a8c378b35cc</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[aws-solutions-architect]]></category>
            <category><![CDATA[aws-s3]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Sun, 19 Jul 2026 16:01:02 GMT</pubDate>
            <atom:updated>2026-07-19T16:01:02.126Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*V7dJl5xwdZzRWq-1HlUjOA.png" /></figure><h3>The Foundation of Cloud Storage</h3><p>When people first hear about Amazon S3, they usually think it’s just another place to store files.</p><p>It’s much more than that.</p><p>Amazon S3 (Simple Storage Service) is one of the foundational services in AWS. Whether you’re hosting a website, storing application data, saving backups, or collecting logs, there’s a good chance S3 is involved somewhere in the architecture.</p><p>Once I started learning AWS, I realized just how many services rely on S3 behind the scenes.</p><h3>Think of S3 Like a Giant Vault</h3><p>The easiest way I think about Amazon S3 is as a giant secure vault.</p><p>Imagine a massive vault with thousands — or even millions — of compartments.</p><p>Inside those compartments, you can store almost anything:</p><ul><li>Documents</li><li>Images</li><li>Videos</li><li>Application files</li><li>Log files</li><li>Database backups</li></ul><p>AWS is responsible for keeping that vault available, durable, and protected while you decide who can access what’s inside.</p><p>Every file you upload is called an <strong>object</strong>, and those objects are stored inside a <strong>bucket</strong>.</p><p>Think of a bucket as a container that organizes all of your objects.</p><h3>Why S3 Is So Important</h3><p>One thing that surprised me while studying for the AWS Solutions Architect certification was how often S3 appeared.</p><p>It isn’t just a storage service.</p><p>It’s a building block for many AWS solutions.</p><p>You’ll see S3 used for</p><ul><li>Website hosting</li><li>Backup and disaster recovery</li><li>Application storage</li><li>CloudTrail log storage</li><li>Static websites</li><li>Analytics</li><li>Machine learning datasets</li></ul><p>The more AWS services you learn, the more often you’ll see S3 connected to them.</p><p>That’s why it’s considered one of the most important AWS services to understand.</p><h3>Built for Durability</h3><p>One of the biggest strengths of Amazon S3 is its durability.</p><p>AWS designs S3 so your data is automatically stored across multiple <strong>Availability Zones</strong> within a Region.</p><p>An Availability Zone is essentially an independent data center.</p><p>Instead of keeping your data in just one location, AWS keeps multiple copies across different Availability Zones.</p><p>If one Availability Zone experiences a failure, your data is still available from another.</p><p>This is one of the reasons S3 is designed for <strong>11 nines of durability (99.999999999%)</strong>.</p><p>In practical terms, that’s an incredibly small chance of losing an object.</p><h3>Security Is Built In</h3><p>Storage is only useful if it’s secure.</p><p>Amazon S3 gives you multiple ways to protect your data.</p><p>You can encrypt objects using server side encryption, where AWS manages the encryption process, or client side encryption, where you encrypt your data before uploading it.</p><p>You can also control access using</p><ul><li>IAM policies</li><li>Bucket policies</li><li>Access Control Lists (ACLs)</li></ul><p>This lets you decide exactly who can view, upload, or delete objects.</p><h3>Features You’ll Use Often</h3><p>As you continue learning AWS, you’ll run into several S3 features repeatedly.</p><p><strong>Versioning</strong></p><p>Versioning keeps previous versions of objects, making it easier to recover files that were accidentally modified or deleted.</p><p><strong>Lifecycle Policies</strong></p><p>Automatically move older objects into cheaper storage classes or delete them after a certain amount of time.</p><p><strong>Pre-Signed URLs</strong></p><p>Create temporary links that allow someone to securely access a private object without making the bucket public.</p><h3>My Biggest Takeaway</h3><p>Before studying AWS, I thought S3 was simply cloud storage.</p><p>After earning my AWS Solutions Architect certification, I realized it’s much more than that.</p><p>It’s one of the foundational services that connects to countless AWS architectures.</p><p>When you start designing cloud solutions, you’ll notice S3 everywhere.</p><p>The more you build in AWS, the more you’ll appreciate just how important this service really is.</p><h3>Final Thoughts</h3><p>If you’re beginning your AWS journey, don’t underestimate Amazon S3.</p><p>It may seem simple at first, but it’s one of the services you’ll use again and again throughout your cloud career.</p><p>Sometimes the most important building blocks are also the simplest.</p><h3>Follow me on the Socials and say Hi</h3><p>Instagram</p><p><a href="https://www.instagram.com/naruto_mma">https://www.instagram.com/naruto_mma</a>/</p><p>X</p><p><a href="https://x.com/Incitelabz">Curtis (@Incitelabz) on X</a></p><p>Youtube</p><p><a href="https://www.youtube.com/@Incit3me"></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a8c378b35cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Passed the AWS Solutions Architect Associate. But That’s Not What Changed My Life]]></title>
            <link>https://medium.com/@incit3me/i-passed-the-aws-solutions-architect-associate-but-thats-not-what-changed-my-life-80f854462b53?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/80f854462b53</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Sat, 18 Jul 2026 19:45:54 GMT</pubDate>
            <atom:updated>2026-07-18T19:45:54.428Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/264/1*xqsbawR4KX-dtEO4S_BPJg.png" /></figure><p>There was a time when I wasn’t planning to learn cloud computing at all.</p><p>Like many people beginning their cybersecurity journey, I thought cloud was something that could wait. It seemed complicated, intimidating, and far removed from where I was.</p><p>Looking back, that would’ve been one of the biggest mistakes I could have made.</p><p>Passing the AWS Certified Solutions Architect Associate wasn’t the moment that changed my life.</p><p>The moment that changed my life was deciding to take the first step.</p><p><strong>Why I Started with the Fundamentals</strong></p><p>I know many people skip the AWS Cloud Practitioner certification because they want to move straight into Solutions Architect.</p><p>I chose a different path because I fundamentally believe in first principles</p><p>Building without fundamentals its like not understanding the building blocks.</p><p>Before designing systems, I wanted to understand the building blocks.</p><p>That’s why I started with AWS Cloud Practitioner.</p><p>Then I earned the AWS AI Practitioner because I believe artificial intelligence is becoming just as fundamental to cloud computing as networking and security.</p><p><strong>Solutions Architect Changed How I Think</strong></p><p>When I began studying for Solutions Architect, a lot happened when I stopped seeing AWS Services as isolated but work together.</p><p>AWS stopped feeling like a collection of unrelated services.</p><p>Instead, it became a connected system I could visualize.</p><p>EC2 wasn’t just virtual machines.</p><p>S3 wasn’t just storage.</p><p>IAM wasn’t just permissions.</p><p>Route 53 wasn’t just DNS.</p><p>Everything had a purpose, and everything worked together.</p><p>I found myself drawing architecture diagrams on paper just to understand how requests flowed through the system.</p><p>That’s when I realized this certification wasn’t teaching me to memorize AWS services.</p><p>It was teaching me to think like an architect.</p><p><strong>Don’t Listen to the Noise</strong></p><p>I heard all the same opinions.</p><p>“Cloud is too hard.”</p><p>“Focus on something easier.”</p><p>“You don’t need AWS yet.”</p><p>I also believe society and our Universities our intimidated by the cloud and those fears translates to its citizens and students.</p><p>If I had listened to those voices, I would’ve stayed exactly where I was.</p><p>Instead, I chose to be uncomfortable for a while.</p><p>That discomfort became growth.</p><p><strong>What Comes Next</strong></p><p>Passing Solutions Architect isn’t the finish line.</p><p>It’s the foundation.</p><p>My next certification is AWS Security Specialty.</p><p>Along the way I’ll continue documenting everything I learn through</p><ul><li>AWS Explained Simply</li><li>Medium articles</li><li>YouTube videos</li><li>Hands-on AWS labs</li><li>TryHackMe cloud security labs</li></ul><p>My goal isn’t simply to collect certifications.</p><p>It’s to understand how modern systems are built, secured, and defended.</p><p><strong>Closing</strong></p><p>Looking back, the hardest part wasn’t the exam.</p><p>It was taking the first step.</p><p>Everything that followed Cloud Practitioner, AI Practitioner, Solutions Architect, and now AWS Security Specialty and it started with one decision.</p><p>Sometimes changing your future isn’t about making a giant leap.</p><p>It’s about taking the first step toward something that once intimidated you.</p><p>That single step has a way of changing everything.</p><p><strong>Follow me on Social media and Say Hi</strong></p><p>Instagram</p><p><a href="https://www.instagram.com/naruto_mma">https://www.instagram.com/naruto_mma</a>/</p><p>X</p><p><a href="https://x.com/Incitelabz">Curtis (@Incitelabz) on X</a></p><p>LinkedIn</p><p><a href="https://www.linkedin.com/in/curtis-bartlett-483b97b8/">Curtis Bartlett - U.S. VETS (United States Veterans Initiative) | LinkedIn</a></p><p>YouTube</p><p><a href="https://www.youtube.com/@Incit3me"></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80f854462b53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Explained Simply EC2. What is Amazon EC2? Understanding Compute in the Cloud]]></title>
            <link>https://medium.com/@incit3me/aws-explained-simply-ec2-what-is-amazon-ec2-understanding-compute-in-the-cloud-ec632634327c?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec632634327c</guid>
            <category><![CDATA[amazon-web-services]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Sun, 28 Jun 2026 16:58:25 GMT</pubDate>
            <atom:updated>2026-06-28T16:58:25.066Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*hhzT2_ApE9K5WTCEpgz8Rg.png" /></figure><p>When I first started learning AWS, one service kept appearing everywhere: Amazon EC2.</p><p>At first it seemed like “just another AWS service,” but the deeper I studied cloud architecture, the more I realized that EC2 is one of the fundamental building blocks of AWS.</p><p>If you’ve ever wondered where your applications actually run in the cloud, EC2 is usually the answer.</p><h3><strong>What is Amazon EC2?</strong></h3><p>Amazon Elastic Compute Cloud (EC2) is a virtual server that runs inside AWS.</p><p>Instead of buying physical servers, installing hardware, and maintaining a data center, AWS allows you to launch virtual machines on demand.</p><p>Think of it as renting computing power whenever you need it.</p><p>You choose the operating system, the amount of CPU and memory, storage, networking, and AWS provisions the infrastructure for you.</p><h3>What can you run on EC2?</h3><p>One of the reasons EC2 is so powerful is its flexibility.</p><p>You can use it to host</p><ul><li>Web applications</li><li>APIs</li><li>Nginx or Apache web servers</li><li>Backend services</li><li>Game servers</li><li>Development environments</li><li>Machine learning workloads</li><li>High-performance computing tasks</li></ul><p>You’re not limited to one type of workload. EC2 is designed to support many different kinds of applications.</p><h3>Why businesses use EC2</h3><p>The biggest advantage isn’t simply having a server.</p><p>It’s having a server that can grow with your business.</p><p>Need additional compute power?</p><p>Launch another instance.</p><p>Traffic increases?</p><p>Pair EC2 with an Auto Scaling Group and Elastic Load Balancer.</p><p>Need a different hardware profile?</p><p>Choose another instance type.</p><p>Instead of waiting weeks to purchase hardware, new infrastructure can be available in minutes.</p><h3>EC2 and the cloud mindset</h3><p>One thing that really clicked for me while studying AWS Solutions Architect is that cloud computing changes how we think about infrastructure.</p><p>Traditional infrastructure often meant planning years ahead.</p><p>Cloud infrastructure lets you provision resources when you need them and release them when you don’t.</p><p>That flexibility is one of the reasons cloud computing has become so widely adopted.</p><h3>Final Thoughts</h3><p>EC2 is much more than a virtual machine.</p><p>It’s the foundation on which many AWS architectures are built.</p><p>As I continue studying AWS Solutions Architect, I’m beginning to see how EC2 works alongside services like S3, IAM, Auto Scaling Groups, Elastic Load Balancers, and RDS to create secure, scalable, and highly available systems.</p><p>This article is part of my <strong>AWS Explained Simply</strong> series, where I’m documenting what I learn while studying cloud architecture.</p><p><strong>If you enjoyed this article</strong></p><p>I document my journey through</p><ul><li>AWS Cloud</li><li>Cybersecurity</li><li>AI</li><li>Python</li><li>Building Incite</li></ul><p>Follow along</p><p>Instagram</p><p><a href="https://www.instagram.com/naruto_mma">https://www.instagram.com/naruto_mma</a>/</p><p>X</p><p><a href="https://x.com/Incitelabz">Curtis (@Incitelabz) on X</a></p><p>LinkedIn</p><p><a href="https://www.linkedin.com/in/curtis-bartlett-483b97b8/">https://www.linkedin.com/in/curtis-bartlett-483b97b8/</a></p><p>YouTube</p><p><a href="https://www.youtube.com/@Incit3me">https://www.youtube.com/@Incit3me</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec632634327c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Passing the AWS AI Practitioner and Seeing the Bigger Picture]]></title>
            <link>https://medium.com/@incit3me/passing-the-aws-ai-practitioner-and-seeing-the-bigger-picture-e5df22fbadda?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5df22fbadda</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 03:05:26 GMT</pubDate>
            <atom:updated>2026-03-21T03:05:26.431Z</atom:updated>
            <content:encoded><![CDATA[<p>How cloud and AI changed the way I see opportunity, technology, and what’s actually possible</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*bUHbbU9Xhy61XhnzOqh1rg.png" /></figure><p>When I passed the AWS AI Practitioner exam, something clicked inside me.</p><p>Not just about AI.</p><p>But about what’s actually possible.</p><p>I grew up in a disadvantaged neighborhood where technology wasn’t something people talked about. The idea that someone like me could build AI or even understand it wasn’t something that felt real. Those opportunities, those ideas, those paths they didn’t seem like they were meant for us.</p><p>But something deep inside me never accepted that.</p><p><strong>Breaking Past Limiting Ideas</strong></p><p>Growing up, you hear a lot of things spoken and unspoken.</p><ul><li>What you’re supposed to be</li><li>What you’re capable of</li><li>What’s realistic</li></ul><p>And if you’re not careful, you start to believe them.</p><p>At one point, I was also listening to what people were saying about the cloud.</p><ul><li>“You shouldn’t trust it.”</li><li>“Why would you put your data on someone else’s servers?”</li></ul><p>But I realized something important</p><p>Avoiding something because it feels unfamiliar can limit your future.</p><p>If I had followed that mindset, I would have capped my potential and fallen behind especially now, with how fast AI is moving.</p><p>The same way I refused to believe that where I grew up defined my intelligence I refused to believe that the cloud was something to avoid.</p><p><strong>Seeing How Everything Connects</strong></p><p>As I studied AWS and AI, I started seeing the bigger picture.</p><p>AI doesn’t exist in isolation.</p><p>It needs infrastructure.</p><p>It needs systems.</p><p>It needs scale.</p><p>That’s where the cloud comes in.</p><p>The cloud isn’t just storage or servers it’s the foundation that allows AI to operate, scale, and become part of real world systems.</p><p>We’re moving into a world where</p><ul><li>A request is made</li><li>AI processes it</li><li>Systems respond automatically</li></ul><p>This isn’t theory anymore</p><p>This is the direction everything is heading.</p><p><strong>The Future Is Being Built Right Now</strong></p><p>AI and cloud are merging, and this will become the standard.</p><p>Just like building websites during the early days of the internet created opportunity, understanding cloud and AI today is opening the same kind of door.</p><p>Not learning it now is like choosing not to build on the internet when it first started.</p><p>You might still get by but you’ll miss where everything is going.</p><p>The cloud is becoming what electricity and oil were to previous generations.</p><p>It powers everything.</p><p><strong>What Changed for Me</strong></p><p>This certification wasn’t about passing a test.</p><p>It was about perspective.</p><p>For the first time, I can clearly see how systems connect:</p><ul><li>Cloud infrastructure</li><li>AI services</li><li>Automation</li><li>Security</li></ul><p>It all fits together.</p><p>And once you see it, you can’t unsee it.</p><p><strong>What’s Next</strong></p><p>Now that I’ve built a foundation with:</p><ul><li>AWS Cloud Practitioner</li><li>AWS AI Practitioner</li></ul><p>My next step is <strong>AWS Solutions Architect</strong>.</p><p>This is where things go deeper where you move from understanding services to designing systems.</p><p>And from there, I’ll move into <strong>cloud security</strong>.</p><p><strong>Final Thought</strong></p><p>In this era, it’s not about where you start.</p><p>It’s about how willing you are to:</p><ul><li>think</li><li>build</li><li>and keep going when things get hard</li></ul><p>Because the opportunity is here.</p><p>And for the first time, it’s more accessible than ever.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5df22fbadda" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Warehouse Floors to the Cloud Passing the AWS Cloud Practitioner Exam]]></title>
            <link>https://medium.com/@incit3me/from-warehouse-floors-to-the-cloud-passing-the-aws-cloud-practitioner-exam-b299a939bde8?source=rss-b5f9871c477a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b299a939bde8</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[career-growth]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Curtis Bartlett]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 23:53:30 GMT</pubDate>
            <atom:updated>2026-03-11T23:53:30.609Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*EP3WC3GiMes0gLxOZLGGEg.png" /></figure><p>I remember studying for the CompTIA Security+ and A+ exams and the grind it took to pass them. Those certifications were more than just credentials to me, they were proof that I had stepped into the world of technology and cybersecurity. For the first time, I could say that I was officially part of the tech industry.</p><p>But passing the <strong>AWS Certified Cloud Practitioner</strong> exam felt different.</p><p>This certification didn’t just represent another step in my journey. It fundamentally changed how I see the future of technology.</p><p>Because today, the cloud is where everything is happening.</p><h3>The Cloud Is the Backbone of the Internet</h3><p>While studying for AWS, I started realizing something profound, the cloud isn’t just another technology trend.</p><p>It’s the backbone of the modern internet.</p><p>The more I learned about cloud infrastructure, the more it reminded me of something much bigger. In many ways, the cloud is like the introduction of electricity to modern society. It powers everything behind the scenes, businesses, applications, data, and increasingly, artificial intelligence.</p><p>It’s where digital civilization is being built.</p><p>In a way, data has become the new oil, and cloud infrastructure is the pipeline that moves it.</p><h3>My Initial Resistance to the Cloud</h3><p>To be honest, when I first started learning about cloud technology, I was hesitant.</p><p>Like many people, I didn’t like the idea of storing important data somewhere “out there.” It felt like giving up control. I preferred the idea of having things locally, where I could see them and manage them directly.</p><p>But as I studied AWS and began understanding how cloud infrastructure actually works, I realized something important:</p><p>People often misunderstand the cloud.</p><p>Avoiding it because it feels unfamiliar can end up limiting your opportunities. The world is moving in this direction whether we like it or not. Choosing not to understand it doesn’t slow the future down — it only puts you further behind it.</p><p>I’m glad I didn’t let that mindset limit me.</p><h3>Seeing AWS Everywhere</h3><p>Another realization came from my life outside of tech.</p><p>Before diving fully into technology, I worked physically demanding jobs. I spent time working at an Amazon warehouse as a dock worker, doing twelve-hour shifts moving freight.</p><p>Later, I drove trucks across the country.</p><p>During those years, I saw Amazon everywhere.</p><p>Amazon trucks. Amazon warehouses. Amazon logistics networks moving products across the country at an incredible scale.</p><p>At the time, I didn’t fully realize it, but Amazon wasn’t just building a logistics empire. Behind the scenes, they were also building one of the most powerful technology infrastructures in the world: <strong>Amazon Web Services</strong>.</p><p>And now I’m studying the very systems that power much of the internet.</p><p>That realization is surreal.</p><h3>The Certification Is Only the Beginning</h3><p>The AWS Cloud Practitioner certification is considered foundational. It’s not meant to make you an expert architect overnight.</p><p>But what it does do is change how you think.</p><p>It opens your eyes to how modern systems are designed, deployed, and scaled across the globe.</p><p>It shifts your perspective from thinking about individual machines to thinking about entire systems.</p><p>And once that shift happens, it changes the way you see technology forever.</p><h3>The Intersection of Cloud, AI, and Cybersecurity</h3><p>One of the most exciting parts of this journey is seeing where cloud computing intersects with other fields I care about deeply <strong>AI and cybersecurity</strong>.</p><p>Cloud platforms make it possible to deploy security systems, monitoring tools, and AI-driven analysis at a scale that would have been impossible just a decade ago.</p><p>The cloud isn’t just infrastructure.</p><p>It’s the foundation for the next wave of innovation.</p><h3>My Next Step AWS AI Practitioner</h3><p>Now that I’ve passed the Cloud Practitioner exam, my next step is studying for the <strong>AWS AI Practitioner certification</strong>.</p><p>Even though it’s still considered foundational, understanding how AI services work in the cloud is incredibly powerful.</p><p>Especially as AI becomes more integrated into cybersecurity, automation, and software development.</p><p>After that, my plan is to move toward the <strong>AWS Solutions Architect certification</strong>, where the real architecture and system design concepts come into play.</p><h3>A Journey I Never Expected</h3><p>To be honest, I never thought I would end up this deep into cloud computing.</p><p>I grew up in a disadvantaged neighborhood where we didn’t even have a computer in the house. Technology wasn’t something that felt accessible.</p><p>But over time, curiosity grew.</p><p>I started learning about computers. Eventually I even built a website.</p><p>And now, years later, I’m studying cloud architecture and AI.</p><p>Life can take unexpected directions.</p><p>Sometimes the only thing required is the willingness to keep learning.</p><h3>Skills Compound Over Time</h3><p>Passing a certification isn’t just about getting a job.</p><p>It’s about building skills that compound over time.</p><p>Every new concept adds another layer of understanding. Eventually those layers connect together in ways you couldn’t have predicted at the beginning.</p><p>That’s what makes this journey exciting.</p><p>And this is only the beginning.</p><h3>Building Toward Something Bigger</h3><p>As I continue studying cloud architecture and artificial intelligence, I’ve also started building small security tools and projects to apply what I’m learning.</p><p>One of the things I’ve realized is that understanding technology deeply comes from building, experimenting, and solving problems in real environments.</p><p>Certifications open the door, but building systems is what truly develops expertise.</p><p>My long-term goal is to combine cloud infrastructure, AI, and cybersecurity to create tools that help protect systems and make security more accessible.</p><p>This is still the early stage of that journey, but every certification, lab, and project is another brick in the foundation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b299a939bde8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>