<?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 Adedamola Olaoye on Medium]]></title>
        <description><![CDATA[Stories by Adedamola Olaoye on Medium]]></description>
        <link>https://medium.com/@adedamolaolaoye027?source=rss-39b99889e029------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s0BlUdeduw7Y-uPsq1A1AA.jpeg</url>
            <title>Stories by Adedamola Olaoye on Medium</title>
            <link>https://medium.com/@adedamolaolaoye027?source=rss-39b99889e029------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:43:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adedamolaolaoye027/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[How I Built an Automated Backup and Audit System on AWS with S3, Lambda, and DynamoDB]]></title>
            <link>https://medium.com/@adedamolaolaoye027/how-i-built-an-automated-backup-and-audit-system-on-aws-with-s3-lambda-and-dynamodb-bbb17cbbd816?source=rss-39b99889e029------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbb17cbbd816</guid>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws-s3]]></category>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-engineering]]></category>
            <dc:creator><![CDATA[Adedamola Olaoye]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 15:40:13 GMT</pubDate>
            <atom:updated>2026-11-18T23:57:54.273Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>I recently built an automated backup and audit system on AWS. A private application server generates data, backups are created automatically every 10 minutes and stored securely in Amazon S3, and every backup is logged in Amazon DynamoDB, with no manual steps in between. The system uses a custom VPC, a bastion host, IAM roles, S3 event notifications, Lambda, and a gateway VPC endpoint.</p><p>I had worked with some of these services before, including on a team-built Expense Tracker, but never wired them together into one complete system.</p><p>There were a lot of moving parts, and I wasn’t sure where to start. So I broke the build into phases and worked through it one layer at a time.</p><p>Here’s how I did it, what went wrong, and what I’d do differently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lg3B3bi6HHHMfjoROq7uaQ.png" /></figure><h3>1. Setting Up the Network</h3><p>I started with the network infrastructure using Amazon Virtual Private Cloud (VPC).</p><p>I created a VPC called project-vpc with two subnets: a public subnet and a private subnet. I also created an Internet Gateway and configured route tables to control how traffic moved through the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u-6-qnk_J0Uf45QymfQqjg.png" /></figure><p>The idea was to keep the application server private rather than expose it directly to the internet.</p><p>I launched a bastion host in the public subnet. This acted as a secure entry point that allowed me to connect to the private application server through SSH. I configured the security groups so that SSH access to the bastion host was restricted to my own IP address, while the application server only accepted SSH connections from the bastion host.</p><p>I also temporarily used a NAT Gateway to give the private server internet access while installing the software and tools I needed.</p><p>After the setup was complete, I deleted the NAT Gateway and configured an S3 Gateway VPC Endpoint. This allowed the private server to communicate with Amazon S3 without needing to send traffic through the public internet.</p><h3>2. Setting Up Secure Storage and Permissions</h3><p>The next phase involved creating an Amazon S3 bucket to store the backup files.</p><p>I created a private bucket called project-backup-adedamola and ensured that Block Public Access was enabled. This meant the backup files would not be publicly accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MQfJxZAGyH03zs6zAYYMUA.png" /></figure><p>I also needed to control what the application server could do with the bucket.</p><p>Instead of storing AWS access keys on the server, I created an IAM role and attached it to the EC2 instance. The role had permission to upload objects to the backups folder in my S3 bucket, but it did not have permission to delete them.</p><p>I tested this by uploading a backup file successfully. I then attempted to delete a backup from the server using the AWS CLI, but the request returned an Access Denied error.</p><p>This confirmed that the permissions were working as intended.</p><p>One thing I learnt from this phase was the importance of giving resources only the permissions they actually need. This is an important security practice known as the principle of least privilege.</p><h3>3. Creating the Backup Automation</h3><p>This was one of the most challenging parts of the project for me.</p><p>I had to work with the Ubuntu command line, create scripts, and understand how the commands I ran on the server interacted with the AWS resources I had created in the console.</p><p>First, I created a sample application that continuously generated data and appended timestamped entries to a log file. I configured it as a systemd service so that it could run in the background, start automatically when the server booted, and restart if it stopped unexpectedly.</p><p>Next, I wrote a Bash script called backup.sh.</p><p>The script performed a few important tasks:</p><ul><li>Collected the application data from the server.</li><li>Compressed the data into a .tar.gz backup file.</li><li>Uploaded the backup file to my S3 bucket using the AWS CLI.</li><li>Recorded whether the upload was successful or failed in a local log file.</li><li>Deleted the local backup file after a successful upload.</li></ul><p>I then configured a cron job to execute the backup script every 10 minutes.</p><p>This was how I automated the backup process without having to manually create and upload backup files each time.</p><h3>4. Automating the Audit Log with Lambda and DynamoDB</h3><p>Storing the backup files in S3 wasn’t enough. Another requirement was to automatically keep a record of every backup uploaded.</p><p>For this, I used Amazon DynamoDB and AWS Lambda.</p><p>I created a DynamoDB table called project-backup-log. This table would store information about each backup, including its name, file size, upload time, and the S3 bucket where it was stored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gFirxcN5T4rhP9T36hoeSA.png" /></figure><p>I then created a Lambda function called project-backup-audit.</p><p>I configured an event notification on my S3 bucket so that whenever a new backup file was uploaded to the backups/ folder, S3 would automatically trigger the Lambda function.</p><p>The Lambda function collected the backup information from the event and wrote it into my DynamoDB table.</p><p>I also created an IAM role for Lambda with permission to write records to the DynamoDB table and send logs to Amazon CloudWatch.</p><p>This was an interesting part of the project because it helped me understand how AWS services can trigger actions in other services without requiring me to manually initiate each step.</p><h3>5. Testing the System</h3><p>After setting everything up, I needed to confirm that the different components worked together.</p><p>I uploaded multiple backup files and checked that they appeared in my S3 bucket. I also checked the DynamoDB table to confirm that corresponding records were being created.</p><p>I checked the Lambda execution logs in CloudWatch to confirm that the function was being invoked successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NBCaCJeacCbvy7Za-cG0A.png" /></figure><p>Another important test was checking whether the application server could still upload backups after the NAT Gateway had been deleted.</p><p>I ran a command to test internet connectivity from the private server. The request to an external website timed out, as expected. However, I was still able to upload a backup to S3, and a corresponding record appeared in DynamoDB.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rIiHnVnahzHNJQjOBfFFGQ.png" /></figure><p>This confirmed that the S3 VPC Endpoint was doing its job.</p><p>Finally, I created an AWS Budget to monitor potential costs and cleaned up the project resources after capturing the required evidence</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_jNv-bv7OW7GSQ_BohfpIA.png" /></figure><h3>6. Challenges and Lessons Learnt</h3><p>I won’t pretend that everything went smoothly.</p><p>The most challenging part was understanding how the backup automation, S3 event notifications, Lambda, and DynamoDB connected. I also had to move between the AWS Management Console and Ubuntu CLI, which required me to understand how the resources I created in one environment interacted with the commands and scripts I ran in another.</p><p>Even something as simple as locating my previously downloaded .pem key file in Ubuntu took some time. I had to find its location, configure its file permissions, and use it to establish my SSH connection.</p><p>However, getting the entire system to work was genuinely exciting. I felt relieved and satisfied, but I was also a little surprised at myself. I remember thinking, ‘I actually did this!’</p><p>My biggest takeaway was gaining a better understanding of how AWS services work together to solve a problem. I also learnt more about interacting with AWS resources from an Ubuntu server using the command line.</p><p>If I had to approach this project again, I would spend more time understanding the architecture before starting the implementation. Having a clearer picture of how the different services connect would make it easier to understand why each resource is needed and how it contributes to the overall solution.</p><h3>7. What I Would Improve</h3><p>Although the system works as designed, there are still things I would improve if I were building this system for a production environment.</p><p>For example, I would consider enabling S3 versioning to protect against accidental changes or overwrites. I would also configure lifecycle policies to manage older backups and control storage costs.</p><p>I would pay more attention to monitoring and alerts so that I could quickly identify failed backups or unexpected activity. I would also review the encryption settings and consider additional security measures depending on the sensitivity of the application data.</p><p>Most importantly, I would revisit the entire implementation and practise building it again without relying on guidance. I want to get to a point where I can confidently explain and reproduce what I have built.</p><h3>Conclusion</h3><p>Building this system taught me more than learning each service on its own ever could. I had used several of these AWS services before, but wiring them into one working solution showed me how much they depend on each other.</p><p>The build had a lot of moving parts, and working through it one layer at a time paid off. Watching every component work together, from the cron job on the private server to the record in DynamoDB, made the effort worthwhile.</p><p>The project gave me a solid foundation in designing and connecting AWS services: network isolation with a VPC, least-privilege access with IAM, event-driven automation with S3 and Lambda, and audit logging with DynamoDB. These are patterns I’ll carry into every build from here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbb17cbbd816" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Secure Two-Tier Network on AWS as a Beginner Cloud Engineer]]></title>
            <link>https://medium.com/@adedamolaolaoye027/building-a-secure-two-tier-network-on-aws-as-a-beginner-cloud-engineer-5ebe4f05c42d?source=rss-39b99889e029------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ebe4f05c42d</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-beginners]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-engineering]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Adedamola Olaoye]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 20:49:21 GMT</pubDate>
            <atom:updated>2026-10-24T20:49:21.706Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started learning about AWS networking, terms like VPC, subnet, route table, Internet Gateway, and bastion host felt like a lot to take in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Urx8ltAEy7_NWDHg7xzHsA.png" /><figcaption>A VPC illustration.</figcaption></figure><p>I could memorise what each term meant, but understanding how they all worked together was a different story.</p><p>Recently, I got the opportunity to put some of these concepts into practice by building a secure two-tier network on AWS. The goal was to create a public server that I could connect to from my laptop and a private server that could only be accessed through the public server.</p><p>It sounded straightforward at first. Getting everything connected, however, required me to pay attention to the details.</p><h3>Understanding What I Was Building</h3><p>Before creating anything, I needed to understand the purpose of the setup.</p><p>A <strong>Virtual Private Cloud (VPC)</strong> is an isolated network within AWS where you can launch and manage resources. Think of it as the main network that contains your servers and the rules governing how they communicate.</p><p>Within the VPC, I created two subnets:</p><ul><li><strong>Public subnet:</strong> This houses the bastion host, which needs to be reachable from my laptop.</li><li><strong>Private subnet:</strong> This houses the private virtual machine, which should not be directly accessible from the internet.</li></ul><p>Both subnets were created in the same Availability Zone.</p><p>I also created an Internet Gateway and configured the public route table to direct internet-bound traffic through it. The private route table, on the other hand, only had the local VPC route. I did not add a route that would give the private subnet direct internet access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zvKvK6aQYfgMKIRSBOYyDA.png" /><figcaption>VPC Resource Map</figcaption></figure><p>Seeing the resources together in the VPC resource map helped me understand how the different pieces fit into the same network.</p><h3>Setting Up the Security Groups</h3><p>Creating the network was only part of the task. I also needed to control who could connect to each server.</p><p>I created two security groups.</p><p>For the bastion host, I allowed SSH traffic on port 22 from my own public IP address. This restricted SSH access to my IP rather than opening it to everyone on the internet.</p><p>For the private virtual machine, I configured the inbound SSH rule to accept connections from the bastion host’s security group.</p><p>This was an important distinction. Instead of allowing SSH connections from any IP address, I was restricting access to a specific security group associated with the bastion host.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xd9DfazwkPhvMpbhBXK1mQ.png" /><figcaption>Bastion Security Group Inbound Rules.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3FuYVBwXordPdjHi3uuipw.png" /><figcaption>Private VM Security Group Inbound Rules.</figcaption></figure><p>These rules helped me understand that securing a server isn’t just about creating it and hoping for the best. You need to think about which connections should be allowed and which should be blocked.</p><h3>Launching the Two Virtual Machines</h3><p>With the network and security groups configured, I launched two EC2 instances.</p><p>The first was the bastion host, placed in the public subnet with a public IP address.</p><p>The second was the private virtual machine, placed in the private subnet without a public IP address.</p><p>Both instances used the same SSH key pair for authentication.</p><p>At this point, I had the network structure I wanted. The next step was to prove that I could access the private machine without exposing it directly to the internet.</p><h3>Connecting to the Private VM Through a Bastion Host</h3><p>A <strong>bastion host</strong> is a server that acts as a controlled entry point into a private network. Instead of connecting directly to a private server from your laptop, you first connect to the bastion host and then use it to reach the private server.</p><p>I started by connecting to the bastion host from my Ubuntu terminal using SSH.</p><p>Once I was connected, I needed to establish another SSH connection to the private VM using its private IP address.</p><p>I used SSH agent forwarding with the -A option for my initial connection. This allowed the bastion host to use my local SSH agent for authentication without requiring me to copy my private key onto the bastion host.</p><p>From the bastion host, I ran:</p><pre>ssh ubuntu@PRIVATE_VM_PRIVATE_IP</pre><p>I replaced PRIVATE_VM_PRIVATE_IP with the actual private IP address of my EC2 instance.</p><p>And then, the connection worked.</p><p>I was inside the private VM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LmcRyb9L0tN3y3BJCjtu1A.png" /><figcaption>Successful SSH connection into the private VM.</figcaption></figure><p>That successful connection was a small but satisfying win. It showed me that the network configuration, security group rules, and SSH authentication were working together as intended.</p><p>It also helped me understand why a bastion host is useful: the private server can remain inaccessible through a direct public connection while still being reachable through a controlled access point.</p><h3>What I Learned From the Exercise</h3><p>This exercise helped me connect concepts I had previously encountered mostly as definitions.</p><p>I learned that creating a VPC and its subnets is only the beginning. Route tables determine where traffic goes, security groups control permitted traffic, and the placement and configuration of an EC2 instance affect how it can be accessed.</p><p>I also learned that a private server does not need a public IP address to be reachable. With the right network configuration and access controls, I could connect to it through a bastion host.</p><p>Most importantly, I saw how the different parts of an AWS network depend on one another. A single misconfiguration can prevent a connection from working, so checking each component matters.</p><p>I’m still learning, and I know there is much more to understand about AWS networking and security. But this exercise made the concepts feel less abstract because I could see them working in a real environment.</p><p>For anyone else learning cloud engineering, I’d say this: don’t stop at learning what the terms mean. Build something, test it, and pay attention to what happens when the pieces come together.</p><p>That’s where the learning really starts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ebe4f05c42d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting Cloud Engineering? Start With These Linux Commands]]></title>
            <link>https://medium.com/@adedamolaolaoye027/starting-cloud-engineering-start-with-these-linux-commands-d656d334e59a?source=rss-39b99889e029------2</link>
            <guid isPermaLink="false">https://medium.com/p/d656d334e59a</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[linux-commands]]></category>
            <category><![CDATA[basic-linux-commands]]></category>
            <category><![CDATA[cloud-engineering]]></category>
            <category><![CDATA[ubuntu]]></category>
            <dc:creator><![CDATA[Adedamola Olaoye]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 00:32:17 GMT</pubDate>
            <atom:updated>2026-10-11T00:32:17.476Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCVNVugXf0Qg8RE1D2ljlg.png" /></figure><p>When I started learning cloud engineering, I quickly realised Linux would be part of the journey.</p><p>I had already mentioned Linux in <a href="https://medium.com/@adedamolaolaoye027/what-i-thought-cloud-engineering-meant-vs-what-ive-learnt-3-weeks-in-395fa2e07d53?sharedUserId=adedamolaolaoye027">my first article</a>, but knowing that Linux was important and actually using it were two very different things.</p><p>I installed Ubuntu on my laptop, opened the terminal, and suddenly found myself staring at a screen full of commands I didn’t fully understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WosttQyfrkK8k3liZAc-1w.png" /></figure><p>So I started with the basics.</p><p>Not because I wanted to memorise every Linux command out there, but because I needed to understand how to actually navigate and work within a Linux environment.</p><p>These are some of the commands I’ve been learning so far.</p><p><strong>1. pwd — Where am I?</strong></p><p>One of the first commands I learned was ‘pwd’.</p><p>It stands for Print Working Directory.</p><p>It tells you the exact directory you’re currently in.</p><p>When you’re moving around different folders in the terminal, knowing where you are becomes pretty important.</p><figure><img alt="**An image showing the `pwd` command in an Ubuntu terminal.**" src="https://cdn-images-1.medium.com/max/377/1*3nYAmXuj4yoNwr7rY13tSw.png" /><figcaption><strong>An image showing the </strong><strong>pwd command in an Ubuntu terminal.</strong></figcaption></figure><h3>2. ls — What’s here?</h3><p>Once I know where I am, I usually want to know what’s inside that directory.</p><p>That’s where ‘ls’ comes in.</p><p>It lists the files and directories in your current location.</p><p>You can also use ‘ls -l’ to see more detailed information about those files and directories.</p><pre>ls | ls -l</pre><h3>3. cd — Moving between directories</h3><p>‘cd’ stands for change directory.</p><p>If I want to move into a folder called Documents, I can use:</p><pre>cd Documents</pre><p>And if I want to go back one level:</p><pre>cd ..</pre><p>This was one of those commands that became much easier once I stopped thinking about it as a technical concept and started thinking of it simply as navigating through folders.</p><h3>4. mkdir — Creating directories</h3><p>mkdir allows you to create a new directory.</p><p>For example:</p><pre>mkdir cloud-learning</pre><p>This creates a new directory called cloud-learning.</p><p>Simple enough, but it becomes useful when you’re organising projects and files from the terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*yXsiRjg9V28gfbF9kh67UA.png" /><figcaption><strong>An image showing the &#39;</strong><strong>mkdir’ command in an Ubuntu terminal.</strong></figcaption></figure><h3>5. touch — Creating files</h3><p>To create an empty file, you can use:</p><pre>touch notes.txt</pre><p>Now you have a file called ‘notes.txt’.</p><p>I’ve found commands like ‘mkdir’ and ‘touch’ useful because they help me get comfortable creating and organising things without relying entirely on a graphical interface.</p><h3>6. cp and mv — Copying and moving</h3><p>Two commands I came across next were:</p><p>‘cp’ and ‘mv’.</p><p>‘cp’ is used to copy files or directories.</p><p>For example:</p><pre>cp notes.txt backup.txt</pre><p>This creates a copy of ‘notes.txt’ called ‘backup.txt’.</p><p>‘mv’ is used to move files or directories. It can also be used to rename them.</p><p>For instance:</p><pre>mv notes.txt linux-notes.txt</pre><p>The file now has a new name.</p><h3>7. rm — Removing files</h3><p>‘rm’ removes files.</p><p>For example:</p><pre>rm notes.txt</pre><p>This removes the file.</p><p>This is one command I learned to be particularly careful with. Unlike moving something to a recycle bin through a graphical interface, commands that remove files can have immediate consequences.</p><p>It’s always worth understanding a command before running it, especially when working with important files or directories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*70PPVEWI9pmbTaZ-MBOQVw.png" /></figure><h3>8. cat — Reading a file</h3><p>If I want to quickly see what’s inside a text file, I can use;</p><pre>cat notes.txt</pre><p>The contents of the file will be displayed directly in the terminal.</p><p>It’s a simple command, but it’s useful when you’re working with configuration files, notes, scripts, and other text-based files.</p><h3>9. grep — Finding specific information</h3><p>‘grep’ is used to search for specific text within files or command output.</p><p>For example:</p><pre>grep &quot;cloud&quot; notes.txt</pre><p>This searches notes.txt for lines containing the word “cloud”.</p><p>As I started learning more about Linux, I realised that being able to find specific information quickly is just as important as knowing how to create or move files.</p><h3>10. sudo — Running commands with elevated privileges</h3><p>You’ll probably come across ‘sudo’ very often when working with Linux.</p><p>It allows a permitted user to run commands with elevated privileges.</p><p>For example:</p><pre>sudo apt update</pre><p>You’ll often need elevated privileges when installing software or making certain system-level changes.</p><p>This is also another reason not to blindly copy and paste commands from the internet. If a command begins with sudo, it’s worth understanding what that command is going to do before running it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*igPz6tSAlGEqf8rNk1MCaQ.png" /></figure><h3>11. apt — Installing and managing software</h3><p>Since I’m learning with Ubuntu, I’ve also been getting familiar with ‘apt’, Ubuntu’s package management tool.</p><p>For example:</p><pre>sudo apt install git</pre><p>This installs Git on the VM.</p><p>This is where Linux started feeling a little more practical to me. I wasn’t just learning commands anymore; I was using them to set up the tools I needed for my learning journey.</p><h3>12. ssh — Connecting to remote machines</h3><p>One command that I know will become increasingly important as I continue learning cloud engineering is ‘ssh’.</p><p>SSH stands for Secure Shell and is commonly used to securely connect to remote machines over a network.</p><p>For cloud engineers, this becomes especially relevant when working with remote servers and cloud-based virtual machines.</p><p>I haven’t mastered everything around SSH yet, but understanding what it does is already helping me connect some of the concepts I’m learning.</p><pre>ssh</pre><h3>13. history — What have I done before?</h3><p>This shows a list of commands you’ve previously run in the terminal. It’s useful when you remember running a command but can’t remember exactly what it was.</p><pre>history</pre><h3>These are only the beginning</h3><p>There are many more Linux commands to learn, and I’m still very much at the beginning of that journey.</p><p>But I’ve realised that I don’t need to memorise every command before I can start becoming comfortable with Linux.</p><p>For me, the goal right now is understanding what these commands do, practising them, and gradually becoming more comfortable using the terminal.</p><p>Some commands that initially looked completely unfamiliar are already starting to feel normal.</p><p>And that’s probably one of the most encouraging parts of learning something new: you don’t always notice yourself improving until you look back and realise that something that once confused you has become something you can actually use.</p><p>I’m still learning Linux, and I’m sure I’ll come across many more commands as I continue my cloud engineering journey.</p><p>For now, these are some of the basics I’m learning and using along the way.</p><p>One command at a time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Efmhahofe6b0kS9yiVIdWA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d656d334e59a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Thought Cloud Engineering Meant vs. What I’ve Learnt 3 Weeks In]]></title>
            <link>https://medium.com/@adedamolaolaoye027/what-i-thought-cloud-engineering-meant-vs-what-ive-learnt-3-weeks-in-395fa2e07d53?source=rss-39b99889e029------2</link>
            <guid isPermaLink="false">https://medium.com/p/395fa2e07d53</guid>
            <category><![CDATA[cloud-beginners]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-engineering]]></category>
            <dc:creator><![CDATA[Adedamola Olaoye]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 13:54:54 GMT</pubDate>
            <atom:updated>2026-09-09T13:54:54.460Z</atom:updated>
            <content:encoded><![CDATA[<p>Two months ago, I never imagined I’d be on my way to becoming a cloud engineer.</p><p><strong>I Thought I Knew What Cloud Engineering Was</strong></p><p>If you had asked me then what cloud engineering was, I probably would have given you one of those confident answers people give when they don’t actually know what they’re talking about. “It’s basically coding stuff and putting it on the cloud, right?”</p><p>Yeah. I thought that was it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2OW3_JikZsJw7s4XLM6RA.jpeg" /></figure><p>Three weeks into my cloud engineering journey, I now realise that I was very wrong. But surprisingly, I’m enjoying every bit of it.</p><p><strong>So, I Started Googling</strong></p><p>When I first decided I wanted to go into cloud engineering, I didn’t immediately start writing code or spinning up servers. I did what any confused beginner with an internet connection would do: I started Googling. And I mean really Googling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xVQDRxgSkVodR-PsbdqJKA.jpeg" /></figure><p>“What exactly is cloud computing?”</p><p>“What does a cloud engineer actually do?”</p><p>“Is cloud engineering coding?”</p><p>“What is AWS?”</p><p>“What is Linux?”</p><p>And somehow, every answer seemed to introduce more things I had never heard of. At some point, I actually felt like I had opened a door expecting one room and walked into an entire building. So I decided to go back to the beginning.</p><p><strong>Wait… What Exactly Is “The Cloud”?</strong></p><p>What exactly is “the cloud”?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sBe-y-4VTQ19bXygURFn1g.jpeg" /></figure><p>I started with resources that explained cloud computing in the simplest possible terms. No complicated technical jargon. No explanations that somehow needed another explanation. I watched YouTube videos, asked AI to explain in the simplest form possible. And slowly, things started making sense.</p><p>I learned that the “cloud” isn’t some mysterious place floating above us (yes, I had to let go of that imagery).</p><p>Cloud computing essentially allows individuals and organisations to access computing resources — such as servers, storage, databases, and networking — over the internet instead of owning and maintaining all that physical infrastructure themselves.</p><p><strong>Then I Discovered AWS, Azure, and GCP</strong></p><p>Then came the cloud platforms — AWS. Microsoft Azure. Google Cloud Platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2zLcqX38gSBz340BNuZrFw.jpeg" /></figure><p>Suddenly, I realised that cloud engineering wasn’t just one thing. There were entire platforms built around providing these cloud services, and cloud engineers work with them to build, deploy, manage, and maintain infrastructure and applications. Okay, interesting.</p><p><strong>And Then Came Linux</strong></p><p>But then I discovered something that made me pause. Linux.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9TiCZAGXKK2vh_g-UI8Efg.jpeg" /></figure><p>Before this journey, I had heard the word Linux plenty of times. But if you’d asked me what Linux actually was, I would probably have given you a very polite smile and changed the subject.</p><p>I didn’t know Linux was an operating system. I definitely didn’t know just how deeply it is embedded in the technology world. And I certainly didn’t expect that learning Linux would become one of my first steps into cloud engineering.</p><p>So, naturally, I went down another rabbit hole.</p><p><strong>Apparently, Linux Has Families Too</strong></p><p>I started learning about Linux distributions — also known as distros — and discovered that there isn’t just one version of Linux sitting somewhere waiting for me to figure it out.</p><p>There are different distributions, each with their own histories, communities, and use cases.</p><p>Ubuntu.</p><p>Debian.</p><p>Red Hat.</p><p>SUSE.</p><p>And then there are the different families and relationships between them.</p><p><strong>How Did I Get Here?</strong></p><p>At this point, I started asking myself, “How did I get here?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*U9DwLzwajRkyaTy_Cuziug.jpeg" /></figure><p>I came into this journey thinking I was going to learn cloud engineering, now I’m researching the history of operating systems. But that’s probably one of the most interesting things I’ve learned so far: Cloud engineering isn’t just about the cloud. There are layers underneath it.</p><p>And the more I learn, the more I realise that understanding those layers makes the bigger picture easier to understand.</p><p><strong>From Watching Tutorials to Actually Doing It</strong></p><p>Eventually, I decided to stop only reading about Linux and actually get my hands dirty. I installed Ubuntu on my laptop.</p><p>And let’s just say… installing Ubuntu was not exactly a walk-in-the-park experience for me.</p><p>There were moments of Googling.</p><p>There were moments of watching YouTube videos.</p><p>There were moments when I stared at my screen, wondering if I had just successfully broken my laptop. But I got through it.</p><p><strong>The Pieces Started Coming Together</strong></p><p>And somewhere between learning Linux commands, navigating the terminal, figuring out Git and GitHub, troubleshooting things that refused to work, and trying to understand how all these different tools connect, something started changing.</p><p>I was no longer just reading definitions; I was beginning to experience the environment I was learning about.</p><p>Before even starting my formal classes, I had already begun doing my own research. I eventually found a school that aligned with where I wanted this journey to take me and registered.</p><p><strong>Three Weeks Later…</strong></p><p>Now, three weeks in, I can confidently say that I understand cloud engineering differently from how I did when I started.</p><p>I now know that there are multiple major cloud platforms, including AWS, Azure, and Google Cloud.</p><p>I understand that Linux is an important part of the cloud engineering ecosystem.</p><p>I’ve learned about different Linux distributions and their families.</p><p>I’ve installed and started using Ubuntu myself.</p><p>I’ve started getting comfortable with the command line.</p><p>I’ve encountered Git and GitHub.</p><p>I’ve spent time learning basic AWS concepts.</p><p>And after exploring my options, I’ve decided to focus my learning on AWS and Azure.</p><p><strong>Do I Understand Everything? Absolutely Not</strong></p><p>Have I figured everything out? Absolutely not.</p><p>In fact, sometimes the more I learn, the more I realise how much I don’t know. But weirdly, that’s no longer intimidating me the way it did at the beginning.</p><p>Because I’m starting to understand that being confused doesn’t necessarily mean you’re not good at something. Sometimes, it just means you’re learning something new.</p><p><strong>If You’re Thinking About Getting Into Cloud Engineering…</strong></p><p>If you’re reading this because you’re thinking about getting into cloud engineering and you’re currently overwhelmed by all the terms — Linux, AWS, Azure, Git, networking, servers, containers, and everything else that seems to come with the territory — trust me, I get it.</p><p>Three weeks ago, I was asking many of the same questions. I still have a lot to learn.</p><p>But I’m also beginning to understand the pieces of the puzzle. And for now, I’m enjoying putting them together, one confusing Google search at a time.</p><p>So, this is where I am three weeks in.</p><p>I came in thinking cloud engineering was about writing code and putting it “in the cloud.” Now I know there’s an entire world underneath that cloud.</p><p>And honestly? I can’t wait to see what the next few weeks reveal.</p><p><strong>This Is Only the Beginning</strong></p><p>This is only the beginning of my journey, and I plan to keep documenting it as I go — the things I learn, the things that confuse me, the mistakes I make, the things I eventually figure out, and hopefully, the lessons that might make someone else’s journey a little easier.</p><p>If you’re also trying to find your way into cloud engineering, stick around. Maybe we can figure it out together.</p><p>Let’s see what the coming days hold.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=395fa2e07d53" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>