<?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 Samuel Ackah on Medium]]></title>
        <description><![CDATA[Stories by Samuel Ackah on Medium]]></description>
        <link>https://medium.com/@sackah08?source=rss-ed0a646bf8f5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6fLjrWyxKqtbzCoc</url>
            <title>Stories by Samuel Ackah on Medium</title>
            <link>https://medium.com/@sackah08?source=rss-ed0a646bf8f5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:46:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sackah08/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[Portfolio Website Deployment]]></title>
            <link>https://medium.com/@sackah08/portfolio-website-deployment-c0cf422ebb51?source=rss-ed0a646bf8f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0cf422ebb51</guid>
            <dc:creator><![CDATA[Samuel Ackah]]></dc:creator>
            <pubDate>Sun, 15 Sep 2024 23:18:12 GMT</pubDate>
            <atom:updated>2024-09-15T23:18:12.123Z</atom:updated>
            <content:encoded><![CDATA[<p>This week, I worked on deploying a <strong>Next.js static site</strong> to AWS S3 using Terraform.</p><p>The task is to deploy James’s Next.js portfolio website on AWS using Infrastructure as Code (IaC) principles with Terraform.</p><ol><li><strong>Downloaded the Next.js Boilerplate</strong>: I started by downloading the template, which included an out folder containing the index.html file that would be deployed to S3.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*ur5jPWxiUYOe2X6Dl8qwEw.png" /></figure><p><strong>2. State Management</strong>:</p><ul><li>I created a <strong>Terraform state file</strong> and securely stored it in <strong>S3</strong> with backup in <strong>DynamoDB</strong>.</li><li>This setup ensures my infrastructure state is saved securely and consistently tracked.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*bphXweADleGxuaxgKB8DNw.png" /></figure><p><strong>3. Resource Creation</strong>:</p><ul><li>Using the main.tf file, I defined the required AWS resources.</li><li>Created an <strong>S3 bucket</strong> to host the static website.</li></ul><p><strong>4. Security Configuration</strong>:</p><ul><li>I configured <strong>bucket ownership</strong> to ensure that all objects, even if uploaded from different AWS accounts, are owned by the bucket owner.</li><li>I set up <strong>fine-tuned access control</strong> by creating policies that govern who can access the bucket.</li><li>Created an <strong>IAM policy</strong> for detailed permissions on the bucket and its objects.</li></ul><p><strong>5. Public Access Setup</strong>:</p><ul><li>AWS S3 blocks public access by default, so I had to configure settings to <strong>allow public access</strong> (ACL) to the bucket, enabling everyone to read objects in the bucket.</li></ul><p><strong>6. CloudFront Configuration</strong>:</p><ul><li>To improve performance and scalability, I created a <strong>Content Delivery Network (CDN)</strong> using <strong>CloudFront</strong>.</li><li><strong>OAI (Origin Access Identity)</strong> was implemented to ensure that only CloudFront can access the S3 bucket, enhancing security and blocking unauthorized access.</li><li>Configured caching behavior for optimal performance and set no geo-restriction.</li></ul><p><strong>7. Deployment and Cleanup</strong>:</p><ul><li>After finalizing the setup, I ran the following Terraform commands:</li><li>terraform init: Initialized the Terraform environment.</li><li>terraform plan: Previewed the changes and confirmed the setup.</li><li>terraform apply: Applied the changes and deployed the resources.</li><li>terraform show: Retrieved the CloudFront domain URL to access the deployed Next.js static site.</li><li>terraform destroy: Cleaned up the resources after confirming everything worked as expected.</li></ul><p>I successfully uploaded my <strong>Next.js static site</strong> to the S3 bucket and deployed it via CloudFront for better performance and scalability.</p><p>This project helped me gain a deeper understanding of <strong>S3 bucket management</strong>, <strong>IAM policies</strong>, <strong>CloudFront setup</strong>, and <strong>Terraform’s integration</strong> with AWS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*stKnrivgBaigJ_H6oMhL0A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*FpwiH6ogA8fNM4er0Ppg_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*gWZZzAtBqvTGKresYcynnA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0cf422ebb51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Infrastructure as code with Terraform]]></title>
            <link>https://medium.com/@sackah08/infrastructure-as-code-with-terraform-1b62f137c330?source=rss-ed0a646bf8f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b62f137c330</guid>
            <dc:creator><![CDATA[Samuel Ackah]]></dc:creator>
            <pubDate>Fri, 06 Sep 2024 21:22:16 GMT</pubDate>
            <atom:updated>2024-09-06T21:22:16.750Z</atom:updated>
            <content:encoded><![CDATA[<p>This week was focused on Infrastructure as Code (IaC) using Terraform, a critical DevOps practice that automates the management and provisioning of infrastructure. Here’s a breakdown of what I learned:</p><p><strong>Infrastructure as Code (IaC)</strong></p><ul><li><strong>Definition</strong>: IaC allows for managing infrastructure resources using machine-readable files rather than manually configuring each resource. This approach offers greater accuracy and consistency by reducing human errors.</li></ul><p><strong>Benefits</strong>:</p><ul><li><strong>Consistency and Accuracy</strong>: Ensures infrastructure remains consistent across environments.</li><li><strong>Version Control</strong>: Tracks changes, allows rollbacks, and manages infrastructure changes like software code.</li></ul><h3>Terraform</h3><ul><li><strong>Overview</strong>: Terraform is an open-source tool that enables infrastructure management across multiple cloud providers (e.g., AWS, GCP, Azure) and hybrid environments.</li><li><strong>Features</strong>:</li><li><strong>Declarative Approach</strong>: You define the desired infrastructure state, and Terraform takes care of the provisioning process.</li><li><strong>Cloud Agnostic</strong>: Unlike tools like AWS CloudFormation, Terraform can manage infrastructure across multiple cloud environments.</li></ul><h3>Key Concepts</h3><ul><li><strong>Provider Configuration</strong>: Defines authentication, region, and other settings to manage specific resources across cloud platforms.</li><li><strong>Resource Management</strong>: Enables management of individual cloud resources like instances (e.g., aws_instance).</li><li><strong>Data Sources</strong>: Allows Terraform to pull in external data, which helps when creating dynamic configurations.</li></ul><p>Terraform + Iac opens the world to endless possibilities</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*KD5zzrxOfXwbiPyFghSn6g.png" /></figure><h3>Terraform Architecture:</h3><p><strong>Three core components</strong> of Terraform:</p><ol><li><strong>Terraform Core</strong>: CLI that runs the Terraform commands.</li><li><strong>Providers</strong>: Interface that allows Terraform to communicate with cloud platforms like AWS, Azure, and GCP.</li><li><strong>State File</strong>: A JSON file that stores information about the current state of the infrastructure managed by Terraform. Keeping the state file secure is essential, often by storing it remotely in AWS S3. It contains sensitive information and is used to track the infrastructure state and dependencies.</li></ol><p>Terraform also supports <strong>Provisioners</strong>, which execute scripts or commands on newly created resources.</p><h3><strong>Terraform Configuration Files</strong>:</h3><ul><li>These files define providers, resources, variables, and outputs in HCL (HashiCorp Configuration Language).</li><li>Key components include:</li><li><strong>Providers</strong>: Define the cloud provider and credentials.</li><li><strong>Resources</strong>: Specify cloud infrastructure services (e.g., EC2 instances).</li><li><strong>Variables</strong>: Allow flexibility and reusability.</li><li><strong>Outputs</strong>: Help retrieve key information about the deployed infrastructure.</li></ul><h3>Terraform Commands</h3><ul><li><strong>Terraform init</strong>: Initializes the working directory with configuration files.</li><li><strong>Terraform plan</strong>: Create an execution plan showing what changes Terraform will apply.</li><li><strong>Terraform apply</strong>: Executes the plan, applying the desired state to the infrastructure.</li><li><strong>Terraform destroy</strong>: Deletes all resources managed by Terraform.</li><li><strong>Terraform fmt/validate</strong>: Formats and validates configuration files to ensure they are in the correct syntax and style.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*L3FoqEzuVqYurVKUXN-F8w.png" /></figure><p><strong>Project: Building a VPC</strong></p><p>I built a VPC with two subnets using Terraform. The VPC architecture included two public subnets for application and web services, along with private subnets for backend databases, all managed through Terraform.</p><p>Next week, I will update my Simple Next.js site using Terraform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b62f137c330" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Journey to Becoming a Cloud Engineer: Weeks 4 and 5]]></title>
            <link>https://medium.com/@sackah08/my-journey-to-becoming-a-cloud-engineer-weeks-4-and-5-38619d41bf15?source=rss-ed0a646bf8f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/38619d41bf15</guid>
            <dc:creator><![CDATA[Samuel Ackah]]></dc:creator>
            <pubDate>Mon, 03 Jun 2024 08:14:43 GMT</pubDate>
            <atom:updated>2024-06-03T08:14:43.892Z</atom:updated>
            <content:encoded><![CDATA[<p>This time, I’m combining Weeks 4 and 5 to share some fascinating insights into my journey. These weeks were packed with learning about Linux, setting up EC2 instances, diving into basic commands, and understanding AWS’s global infrastructure.</p><p><strong>Week 4: Linux Setup and EC2 Connection</strong></p><p>In Week 4, I focused on getting comfortable with the Linux operating system. I learned about the hierarchical structure of the Linux file system, akin to an inverted tree, which is essential for efficient navigation and file management. Some of the fundamental commands I practiced included:</p><ul><li><strong>PWD (Print Working Directory):</strong> Displays the current directory.</li><li><strong>CD (Change Directory):</strong> Navigate through directories.</li><li><strong>LS (List):</strong> Lists directory contents.</li><li><strong>CD .. (Go Back):</strong> Moves up one directory level.</li><li><strong>Touch:</strong> Creates an empty file.</li><li><strong>Nano:</strong> Edits files using the Nano text editor, with Control + O to save and Control + X to exit.</li><li><strong>Cat:</strong> Displays file contents.</li><li><strong>Chmod (Change Mode):</strong> Changes file permissions</li></ul><p><strong>Connecting to EC2/S3 with Linux</strong></p><p>A significant task was learning to connect to an Iam role using EC2 instance. This involved launching an EC2 instance on AWS and connecting via with a command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*ZoLw_VxjTkVzqghYNpN6gA.png" /></figure><p>Week 5: AWS Global Infrastructure and VPC Design.</p><p>For the hands-on project in Week 5, I designed a VPC with a CIDR block and implemented both public and private subnets across multiple Availability Zones (AZs) to ensure high availability. Here are the key steps and components of the design:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*1t7SGrrCjGv1yWMU5ypCpQ.png" /></figure><ol><li><strong>VPC Design: </strong>Created a VPC with a CIDR block (10.0.0.0/16).</li><li><strong>Subnets:</strong>Designed two public subnets, one in each AZ, for high availability. Also designed four private subnets, two in each AZ, for the application and databases.</li><li><strong>Internet Access:</strong>Ensured public subnets have access to the internet via an Internet Gateway.</li><li><strong>NAT Gateway: </strong>Implemented a NAT Gateway in one of the public subnets, allowing instances in private subnets to access the internet for updates.</li><li><strong>Route Tables: </strong>Configured route tables for both public and private subnets to manage traffic flow.</li><li><strong>Security: </strong>Added security groups and NACLs (Network ACLs) for additional security layers.</li></ol><p>The VPC design was visualized and included key components such as subnets, route tables, Internet Gateways, NAT Gateways, and security configurations to ensure a robust and secure network architecture</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38619d41bf15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Journey to Becoming a Cloud Engineer: Week 3]]></title>
            <link>https://medium.com/@sackah08/my-journey-to-becoming-a-cloud-engineer-week-3-24a190f6afb5?source=rss-ed0a646bf8f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/24a190f6afb5</guid>
            <dc:creator><![CDATA[Samuel Ackah]]></dc:creator>
            <pubDate>Fri, 31 May 2024 20:28:38 GMT</pubDate>
            <atom:updated>2024-05-31T20:28:38.072Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to Week 3 of my journey to becoming a cloud engineer! This week, I explored different architectural patterns: Monolithic, Microservices, and Serverless. Each has its unique advantages and challenges, and I had the opportunity to work on hands-on projects to deepen my understanding.</p><h4>Understanding Monolithic Architecture</h4><p>I started with monolithic architecture. In this traditional approach, the entire application is built as a single, indivisible unit. All parts of the application, from the user interface to the business logic and data handling, are combined.</p><p><strong>Pros:</strong></p><ul><li>Simplicity and uniformity.</li></ul><p><strong>Cons:</strong></p><ul><li>Scalability and flexibility issues.</li></ul><h4>Moving to Microservices Architecture</h4><p>Next, I explored microservices architecture. This method breaks down applications into smaller, self-contained services. Each service operates independently but works together to support the entire application.</p><p><strong>Pros:</strong></p><ul><li>Scalability and flexibility, as services can be deployed independently.</li></ul><p><strong>Cons:</strong></p><ul><li>Increased complexity and management challenges.</li></ul><h4>Exploring Serverless Architecture</h4><p>Finally, I learned about serverless architecture. In this approach, developers focus solely on writing code, while the cloud provider manages the infrastructure. It operates on a pay-as-you-go model, which is cost-effective and efficient.</p><p><strong>Pros:</strong></p><ul><li>Cost-effective, automatic scaling, and reduced operational overhead.</li></ul><p><strong>Cons:</strong></p><ul><li>Not suitable for all application types due to its stateless nature and potential latency issues.</li></ul><h4>Learning About Cloud Storage Options</h4><p>I also delved into various cloud storage options:</p><ol><li><strong>File Storage:</strong> Organizes data in a hierarchy of files and folders.</li><li><strong>Block Storage:</strong> Splits data into uniformly sized blocks.</li><li><strong>Object Storage:</strong> Manages data as objects, ideal for large sets of unstructured data.</li></ol><h4>The Importance of Caching</h4><p>Caching improves performance by temporarily storing frequently accessed data. This reduces the load on the backend and speeds up response times.</p><h4>Hands-On Projects</h4><p>This week’s projects focused on applying these architectural patterns in real scenarios:</p><ol><li><strong>Monolithic Architecture:</strong> Required deploying the entire application together, making it less scalable and flexible.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*uZAsZz9H8wzL0AAu0deqAA.png" /></figure><p><strong>Microservices Architecture:</strong></p><ul><li>Improved scalability and flexibility by allowing independent deployment of services.</li><li>Used both recreational and NoSQL databases.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*p9n4f8c043nVxDuAq8hiIw.png" /></figure><p>Serverless Architecture:</p><p>Focused on coding while the platform handled infrastructure.<br>Cost-effective with a pay-as-you-go model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*FIR9Hpid8Q2iXbRZie_Jlg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*Ng90X8LuknYs-eIb6mpuwQ.png" /></figure><p>broke down the e-commerce application into independent services such as user management, product catalog, order processing, and payment handling. Each service was deployed independently, which made it easier to scale specific parts of the application as needed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*ouFvQGIeNCoxrqWXIoU25w.png" /></figure><p>focused on creating a serverless backend for the e-commerce application. I utilized AWS Lambda to handle functions such as user authentication, product listing, and order processing.</p><p>Additionally, I designed the architecture for a video-sharing platform, applying the principles I learned. These projects provided a comprehensive understanding of how different architectures can be applied to real-world scenarios, highlighting their advantages and limitation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*qLCi7JLr72jnBwxkreJuOQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24a190f6afb5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 2-Git and Cloud Architecture]]></title>
            <link>https://medium.com/@sackah08/week-2-git-and-cloud-architecture-c4989b0e50da?source=rss-ed0a646bf8f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4989b0e50da</guid>
            <dc:creator><![CDATA[Samuel Ackah]]></dc:creator>
            <pubDate>Mon, 27 May 2024 22:40:55 GMT</pubDate>
            <atom:updated>2024-05-27T22:40:55.995Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SumY1azBJdnroU9T.png" /></figure><p>This week, I delved into version control systems, Git, and cloud architecture. It was a week filled with research, learning, and a few “Yay, finally got it!” moments.</p><h4>Version Control Systems</h4><p>Understanding version control systems was a crucial part of my learning this week. These systems help manage and track changes to code over time, allowing multiple people to collaborate on a project. It’s not just a tool but a fundamental aspect of modern software development, playing a crucial role in debugging and understanding the evolution of a program.</p><p>I learned about the three main components:</p><ul><li>Repository: The full database where everything is stored.</li><li>Commit: A snapshot of your files at a particular point in time, reflecting changes made.</li><li>Branch: A parallel version of the repository, created to develop features, fix bugs, or experiment.</li></ul><p>I also learned about best practices, such as writing clear and descriptive commit messages, committing changes frequently to avoid large, complicated changes, and using branches and bug fixes.</p><h4>Git and GitHub</h4><p>Git, a distributed version control system, is designed to handle projects of any size with speed and efficiency. It allows developers to have a full history of the codebase, enabling autonomous work and redundancy. GitHub, a web-based platform, facilitates version control and collaboration, tracking changes in source code during software development.</p><p>I spent time learning Git commands for cloning repositories, making commits, branching, and merging. This hands-on experience was both challenging and rewarding, and I had several “Yay, finally got it!” moments as I navigated through these processes.</p><h4>Cloud Architecture</h4><p>Cloud architecture refers to how various cloud components such as hardware, software, storage, and virtual resources integrate and work together to create a cloud system and environment. The purpose of cloud architecture is to act as a blueprint for how cloud components work together and to follow best architecture patterns and practices.</p><h4>System Design</h4><p>System design involves creating software systems that can scale reliably and upgrade efficiently, especially in the context of the cloud. This week, I applied my understanding of these concepts in a practical project.</p><h4>Project: Basic Cloud Architecture</h4><p>This week, I developed a conceptual design for a cloud infrastructure supporting a web application. Here’s how it works:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*T-OYgsFE3eS3RMVTkFSnwQ.png" /></figure><ol><li>DNS Server: The user contacts a DNS server, which provides the IP address.</li><li>Web Server Request: The browser sends a request for web documents (HTML) to the web server.</li><li>Load Balancer: Distributes incoming traffic to multiple servers to prevent any single server from becoming overwhelmed. I chose horizontal scaling allows adding more load balancers to manage increased traffic.</li><li>Front-End Servers: Serve static content and handle user interactions. i chose horizontal scaling allows adding more servers to handle more concurrent users and provide redundancy.</li><li>Back-End Servers: Handle dynamic content generation, business logic, and database interactions. i chose horizontal scaling allows handling increased processing demands and provides high availability.</li></ol><p>Summary: This architecture ensures high availability, scalability, and performance. Load balancers distribute traffic efficiently, while horizontally scaling web and application servers ensures that the application can handle increasing loads.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4989b0e50da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Engineer Academy — Week 1 Cloud Fundamentals]]></title>
            <link>https://medium.com/@sackah08/cloud-engineer-academy-week-1-cloud-fundamentals-178ac45a362c?source=rss-ed0a646bf8f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/178ac45a362c</guid>
            <dc:creator><![CDATA[Samuel Ackah]]></dc:creator>
            <pubDate>Wed, 22 May 2024 16:59:02 GMT</pubDate>
            <atom:updated>2024-05-22T16:59:02.270Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Engineer Academy — Week 1 Cloud Fundamentals</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/0*RWSqMfB7QhRGdj-G.jpeg" /></figure><p>Welcome to the first week of my journey to becoming a cloud engineer! This week, I focused on understanding the fundamentals of cloud computing. Here’s what I learned:</p><h4>Starting with the Basics</h4><h4>What is Cloud Computing?</h4><p>Cloud computing is the delivery of computer services over the internet. It includes services like servers, storage, databases, networking, software, analytics, and AI. This technology is transforming how businesses operate and manage data.</p><h4>Key Cloud Service Models</h4><ol><li>Infrastructure as a Service (IaaS): The cloud provider manages the hardware, servers, storage, and other infrastructure elements, allowing clients to rent these resources over the internet.</li><li>Platform as a Service (PaaS): This model allows you to build, test, and deploy applications while the cloud provider manages the underlying infrastructure.</li><li>Software as a Service (SaaS): Software applications are delivered over the internet on a subscription basis, allowing users to access the software without installing it on their computers.</li></ol><h4>Key Characteristics of Cloud Computing</h4><ol><li>On-demand Self-Service: Users can automatically provision computing resources such as server time and network storage.</li><li>Resource Pooling: Cloud provider resources are pooled to serve multiple customers, both physically and virtually.</li><li>Rapid Elasticity or Scalability: Resources can be scaled up or down as needed.</li><li>Measured Service: Resource usage is monitored, controlled, and reported, ensuring transparency and accountability.</li></ol><h4>Cloud Deployment Models</h4><ol><li>Public Cloud: Available to anyone, offering vast scalability and operated by third-party cloud service providers.</li><li>Private Cloud: Dedicated to a single organization, providing tight security.</li><li>Hybrid Cloud: Combines public and private clouds, allowing organizations to use public cloud services for some tasks while keeping sensitive operations on a private cloud.</li></ol><h4>Software Delivery Lifecycle (SDLC)</h4><p>The SDLC is a methodology for building and delivering software. It includes stages such as planning, designing, coding, testing, and deployment.</p><h4>Understanding the Internet</h4><p>The internet is like a highway connecting various computers and devices. Data travels through the internet in smaller units called data packets, which are reassembled at the destination.</p><h4>Virtualization</h4><p>Virtualization involves creating virtual versions of physical components such as servers, storage, networks, and desktops. It’s like a hotel with rooms decorated to suit different tenants’ needs, allowing each tenant to live independently. There are four main types of virtualization:</p><ol><li>Server Virtualization: Creating smaller, independent servers.</li><li>Storage Virtualization: Combining storage capacity from physical devices.</li><li>Network Virtualization: Merging network and software resources into a virtual network.</li><li>Desktop Virtualization: Providing virtual workspaces in the cloud.</li></ol><h4>Networking</h4><p>Networking is the practice of connecting multiple computers, servers, and other devices to share data and resources.</p><h4>Projects</h4><p>I worked on three projects this week:</p><ol><li>HTTP GET Request: Retrieving web page data and analyzing HTTP.</li><li>Tracing Path Packets: Identifying where packets are delayed or lost to diagnose network connectivity issues.</li><li>Finding Public IP Address and Ping Requests: Understanding how to find and test network connections.</li></ol><p>In summary, these fundamentals have deepened my understanding of cloud computing. I’m excited to continue this journey and share my progress with you in the coming weeks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=178ac45a362c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>