<?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 Erika Thomas on Medium]]></title>
        <description><![CDATA[Stories by Erika Thomas on Medium]]></description>
        <link>https://medium.com/@thomas.erikaj?source=rss-6b453562aaea------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hVjAE3wq666YCMGZaatKmQ.jpeg</url>
            <title>Stories by Erika Thomas on Medium</title>
            <link>https://medium.com/@thomas.erikaj?source=rss-6b453562aaea------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:55:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thomas.erikaj/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[“Mastering Cloud Deployment: Step-by-Step Guide to Launching an Auto-Scaling Web Server”]]></title>
            <link>https://medium.com/@thomas.erikaj/mastering-cloud-deployment-step-by-step-guide-to-launching-an-auto-scaling-web-server-48913cc57c1e?source=rss-6b453562aaea------2</link>
            <guid isPermaLink="false">https://medium.com/p/48913cc57c1e</guid>
            <dc:creator><![CDATA[Erika Thomas]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 01:47:00 GMT</pubDate>
            <atom:updated>2023-07-07T01:47:00.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MsnSbnbqQdid2ksamicNUw.png" /></figure><p>In this project, you will learn how to build a scalable web infrastructure using Amazon Web Services (AWS). Follow these step-by-step instructions to create, scale, and secure your own auto-scaling web server.</p><p><strong>Create a Virtual Private Cloud (VPC) and Subnets</strong></p><p>Log in to the AWS Management Console and navigate to the VPC service.<br>Create a new VPC and name it according to your preference.<br>Within the VPC, create two public subnets, each in a different availability zone for high availability.</p><p><strong>Launch EC2 Instances in Auto Scaling Group</strong></p><p>Go to the EC2 service in the AWS Management Console.<br>Launch two EC2 instances using a free-tier eligible Amazon Machine Image (AMI). Place each instance in one of the public subnets created earlier.<br>Set up an Auto Scaling Group (ASG) with the desired capacity, minimum and maximum size, and associate it with the subnets.</p><p><strong>Configure Security Group for Web Server</strong></p><p>Create a new security group for the EC2 instances.<br>Configure inbound rules to allow HTTP (port 80) traffic from the internet.<br>Optionally, allow SSH (port 22) access for administrative purposes.</p><p><strong>Bootstrap Web Server or Create Custom AMI</strong></p><p>Choose an operating system of your choice for the EC2 instances.<br>If bootstrapping, provide a user data script that installs a web server (e.g., Apache or Nginx) and serves a static web page. The script can be provided during instance launch.<br>Alternatively, create a custom AMI that already includes the necessary web server and static web page.</p><p><strong>Create Public Route Table and Associate Subnets</strong></p><p>Go to the VPC service in the AWS Management Console.<br>Create a public route table and associate it with the VPC.<br>Add a route to the internet gateway (IGW) for internet connectivity.<br>Associate the public route table with the two public subnets.</p><p><strong>Test Your Web Server</strong></p><p>Obtain the public IP addresses or domain names of your EC2 instances.<br>Open a web browser and enter the public IP address or domain name of one of the instances.<br>If everything is set up correctly, you should see the static web page displayed in the browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*ZtWyWXLj4NhNiTHOUkKFFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*HLGsclq4CNfxAhax8UZ6gA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dX8vFqZxX2MuX_Zij690ug.png" /></figure><h3><em>By following these steps, you will have created a scalable web infrastructure using AWS, with auto-scaling EC2 instances, security groups, and a public route table for internet connectivity.</em></h3><p><em>Happy building and scaling your web server!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48913cc57c1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Step-by-Step Guide: Creating a DynamoDB Table for Latest Movie Releases]]></title>
            <link>https://medium.com/@thomas.erikaj/step-by-step-guide-creating-a-dynamodb-table-for-latest-movie-releases-63b2f0ea2a7d?source=rss-6b453562aaea------2</link>
            <guid isPermaLink="false">https://medium.com/p/63b2f0ea2a7d</guid>
            <dc:creator><![CDATA[Erika Thomas]]></dc:creator>
            <pubDate>Thu, 29 Jun 2023 23:36:19 GMT</pubDate>
            <atom:updated>2023-06-30T13:47:56.383Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*fH0-uY_bEpTgihNU.png" /></figure><h3><strong>But first what is DynamoDB (KIDS VERSION)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*twPrTDvTjy2QkRCw" /><figcaption>Photo by <a href="https://unsplash.com/@norevisions?utm_source=medium&amp;utm_medium=referral">No Revisions</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine you have a notebook where you can write down different things you want to remember. DynamoDB is like a super-smart notebook that can store lots of information, just like a big library.</p><p>In DynamoDB, instead of pages, we have tables. Each table is like a separate book. You can give each table a name, like “Animals” or “Toys.”</p><p>Inside each table, we have rows and columns. Rows are like entries in a dictionary, and columns are like different pieces of information you want to remember.</p><p>Let’s say we have an “Animals” table. Each row in the table can represent a different animal. For example, we can have a row for a lion, another row for a tiger, and so on.</p><p>In each row, we have different columns to store information about the animal. We can have columns for the animal’s name, color, size, and any other details we want to remember.</p><p>The cool thing about DynamoDB is that it can store a huge number of rows and columns. It’s really fast and can handle a lot of information.</p><p>Also, DynamoDB is very smart. It can quickly find and retrieve information. For example, if you want to know the color of a lion, DynamoDB can look it up in the “Animals” table and tell you right away.</p><p>DynamoDB is often used by computer programmers and companies to store and manage data. It’s a powerful tool that helps them keep track of lots of information easily.</p><p>So, in simple terms, DynamoDB is like a super-smart notebook that stores information in tables, rows, and columns. It helps us organize and find information quickly.</p><p><strong>Introduction</strong>: In this tutorial, we will walk through the process of creating a DynamoDB table to store information about the latest movie releases. We will cover the steps required to set up the table, add movie entries, create an EC2 instance with the necessary permissions, and validate the read-only access to the DynamoDB table using the AWS CLI.</p><p><strong>Step 1: Create a DynamoDB Table</strong></p><ol><li>Sign in to the AWS Management Console and open the DynamoDB service.</li><li>Click on “Create table” and provide a suitable name for your table, such as “LatestMovieReleases.”</li><li>Set the primary key as “title” with the data type as “String.”</li><li>Optionally, you can configure additional settings based on your requirements, such as provisioned throughput or auto scaling. For this tutorial, the default settings will suffice.</li><li>Click on “Create” to create the DynamoDB table.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*Fg-dWVqIeDSt_aY1EGjZOw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*0UJe_3JOyAKnsSDMf8ViOw.png" /></figure><p><strong>Step 2: Add Movie Releases to the Table</strong></p><ol><li>Once the table is created, navigate to the “Items” tab in the DynamoDB console.</li><li>Click on “Create item” and enter the details of the first movie release, including the title, genre, release date, and rating.</li><li>Repeat the above step to add a total of 10 latest movie releases to the table.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KUr1jgaSDg-hQnAEckDmTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*FrDq59dISLzc__6jFUFPRw.png" /></figure><p><strong>Step 3: Create an EC2 Instance</strong></p><ol><li>Open the Amazon EC2 service in the AWS Management Console.</li><li>Click on “Launch instance” and choose the Amazon Machine Image (AMI) suitable for your needs.</li><li>Select the “t2.micro” instance type and click “Next.”</li><li>Configure the instance details as required and proceed to the next steps.</li><li>In the “Configure Security Group” section, ensure that you allow SSH access and any other necessary inbound traffic.</li><li>Review and launch the instance, following the on-screen prompts.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*X0j-tmfwoTgNbMrx7jjBnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*KhODIHKYOuyyHRWKz5VYNA.png" /></figure><p><strong>Step 4: Grant EC2 Instance Read Access to DynamoDB</strong></p><ol><li>While the EC2 instance is being launched, navigate to the IAM service in the AWS Management Console.</li><li>Create a new IAM role or choose an existing role that will be associated with the EC2 instance.</li><li>Configure the role’s permissions, ensuring it has read access to the DynamoDB table.</li><li>Attach the IAM role to the EC2 instance by selecting it during the instance launch or associating it later through the EC2 console.</li></ol><p><strong>Step 5: Scan the DynamoDB Table using AWS CLI</strong></p><ol><li>Connect to your EC2 instance via SSH using an SSH client like PuTTY or the built-in terminal on macOS/Linux.</li><li>Install and configure the AWS CLI on the EC2 instance, if not already done.</li><li>Open the terminal or SSH session and run the following command to scan the DynamoDB table:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*fKlGI4p0ypZrodV0fMBiAw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSAlH3LgkTRtvjjOTFuzyw.png" /></figure><ol><li>The command will retrieve and display all the items stored in the DynamoDB table.</li></ol><p><strong>Step 6: Validate Write Restrictions using AWS CLI</strong></p><ol><li>To validate that writing to the DynamoDB table is restricted, run the following command:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*jnAnopqqsTV90JxoxzBbKQ.png" /></figure><p><strong>You should receive an error message indicating that the operation was denied due to lack of write permissions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X-3gdzMPcPBIyDlLovrrGg.png" /></figure><p><strong>Conclusion</strong>: Congratulations! You have successfully created a DynamoDB table for storing the latest movie releases, added movie entries, created an EC2 instance with read access to DynamoDB, and verified the read-only access using the AWS CLI. This setup allows you to easily manage and retrieve movie information from your DynamoDB table. Feel free to explore further by performing additional operations on the DynamoDB table, such as querying specific movie releases, updating existing entries, or deleting movies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ep_2kNkK_qZxXhtk" /><figcaption>Photo by <a href="https://unsplash.com/@fkaregan?utm_source=medium&amp;utm_medium=referral">Samuel Regan-Asante</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63b2f0ea2a7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Application Scaling and Traffic Distrubution on EC2 Instance]]></title>
            <link>https://medium.com/@thomas.erikaj/application-scaling-and-traffic-distrubution-on-ec2-instance-3ff0effcfe02?source=rss-6b453562aaea------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ff0effcfe02</guid>
            <dc:creator><![CDATA[Erika Thomas]]></dc:creator>
            <pubDate>Wed, 28 Jun 2023 01:02:36 GMT</pubDate>
            <atom:updated>2023-06-28T01:02:36.606Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wTxgjMLt8bf-BjS0fANqBw.png" /></figure><p>In today’s post, we’ll explore some essential elements of managing instances in a cloud environment. Let’s dive in!</p><p>1️⃣ Creating an Auto Scaling Group:<br>Auto Scaling Groups (ASGs) are a fundamental component for maintaining the availability and scalability of instances. By automatically adjusting the number of instances based on demand, ASGs ensure optimal performance. Implementing an ASG involves defining launch configurations, setting scaling policies, and establishing health checks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tXuJwSO4JZXSvXujHOKo1w.png" /></figure><p>2️⃣ Network Setup:<br>To ensure secure and efficient communication between instances, a well-designed network configuration is crucial. It typically includes the following components:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*T-Y0xd7HTRC6rhM1CKHVdQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*b80Vm-qx2iu0zuJZh2zU0A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*Iuz8uZFl23fXves57jZVTg.png" /></figure><p>3️⃣ Confirming Apache HTTPD:<br>Once your instances are up and running, it’s crucial to ensure that essential services are functioning correctly. In the case of an Apache HTTP Server (HTTPD), you can verify its status using various methods. You might check the server logs, review the running processes, or even perform a simple HTTP request to validate that the server responds properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vYAdxPt9aUJH4i_nFihzOQ.png" /></figure><p>Remember, regularly confirming the health of crucial services like Apache HTTPD is vital for maintaining a stable and reliable environment.</p><p>That’s it for today’s post! We covered the creation of an Auto Scaling Group, network setup involving security groups, subnets, and load balancers, and the importance of confirming Apache HTTPD functionality. Stay tuned for more exciting topics on managing instances in the cloud. Happy scaling and networking! 🌟</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ff0effcfe02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create a t2.micro EC2 Instance with Apache Webserver]]></title>
            <link>https://medium.com/@thomas.erikaj/create-a-t2-micro-ec2-instance-with-apache-webserver-74a05453322a?source=rss-6b453562aaea------2</link>
            <guid isPermaLink="false">https://medium.com/p/74a05453322a</guid>
            <category><![CDATA[amazon-linux]]></category>
            <category><![CDATA[t2]]></category>
            <category><![CDATA[micro]]></category>
            <dc:creator><![CDATA[Erika Thomas]]></dc:creator>
            <pubDate>Tue, 13 Jun 2023 19:05:20 GMT</pubDate>
            <atom:updated>2023-06-14T16:39:14.007Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/321/1*QeKHeGcS2pIVp-uRO1Yv3w.png" /></figure><p><em>To create a t2.micro EC2 instance with Apache webserver, you can follow the steps outlined below: (amazon linux AMI)</em></p><p><strong>Step 1: Sign in to the AWS Management Console Go to the AWS Management Console (</strong><a href="https://aws.amazon.com/console"><strong>https://aws.amazon.com/console</strong></a><strong>) and sign in to your AWS account.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*eXQImfo8ooP-AkinGM43JA.png" /></figure><p><strong>Step 2: Open EC2 service Once you’re signed in, navigate to the EC2 service by clicking on “Services” in the top navigation bar and selecting “EC2” under the “Compute” section.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*-NHdLX6wTFHGF6mZ40MIlw.png" /></figure><p><strong>Step 3: Launch Instance In the EC2 dashboard, click on the “Launch Instance” button to start the instance creation process.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*zmsqf2n0C6F5roo5pboNdA.png" /></figure><p><strong>Step 4: Choose an Amazon Machine Image (AMI) On the “Step 1: Choose an Amazon Machine Image (AMI)” page, select an Amazon Linux 2 AMI. You can find it by searching for “Amazon Linux 2” in the search bar. Choose the desired version and click “Select”.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*zhM0MDkNMS_o7fXxpoKoKA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*um4Gou1ADMEkO17rEikQEQ.png" /></figure><p><strong>Step 5: Choose an Instance Type On the “Step 2: Choose an Instance Type” page, scroll down and select the “t2.micro” instance type. This is a free-tier eligible instance. Click “Next: Configure Instance Details” to proceed.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*yzz3A01QlLXzPiGdJm3z_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*auQXjPojyxijleWuflj95Q.png" /></figure><p>Step 6: Configure Instance Details You can leave the default configuration options on this page as they are. If you need to make any specific changes, you can do so here. Once you’re ready, click “Next: Add Storage”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*Z6Cn56lo-uCZN6E8UofNhw.png" /></figure><p><strong>Step 7: Add Storage The default storage size for t2.micro instances is usually sufficient for most purposes. You can adjust the storage size if needed. When you’re done, click “Next: Add Tags”.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*BswpXXP5Mfsaf1BJ9zjjfg.png" /></figure><p><strong>Step 8: Add Tags (Optional) Tags are key-value pairs that can be added to resources for better organization and management. You can add tags if desired, but they are not required. Click “Next: Configure Security Group” to continue.</strong></p><p><strong>Step 9: Configure Security Group On the “Step 6: Configure Security Group” page, you need to configure the inbound rules to allow incoming HTTP (port 80) traffic. Click “Add Rule” and select “HTTP” from the “Type” dropdown. You can leave the source as “Anywhere” (0.0.0.0/0) or customize it as per your requirements. Click “Review and Launch” when you’re ready.</strong></p><p><strong>Also in the the text editor, enter the desired script content.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*6R4Af04YutbggZCk0b7leQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*Yq9bkobKm8dP8Z8IGjjQcA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*CPDXpM-xMpGMpg90Foys8g.png" /></figure><p><strong>Step 10: Review Instance Launch Review the instance details to ensure everything is configured correctly. If you need to make any changes, you can go back to the respective steps and modify them. Once you’re ready, click “Launch”.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SU_PtPOiCXh410OP85dDCw.png" /></figure><p><strong>Step 11: Create a new key pair or choose an existing one Select an existing key pair or create a new one. This key pair will be used to securely connect to your EC2 instance via SSH. Follow the prompts to create or select a key pair, and then click “Launch Instances”.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*11C_q4NnkLz0-4afmKpU5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*zmsqf2n0C6F5roo5pboNdA.png" /></figure><p><strong>Step 12: Launch status After launching the instance, you’ll see a confirmation screen. From here, you can either view the instances directly or proceed to other tasks.</strong></p><p><strong>Step 13: Connect to the instance once the instance is running,</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*jPkhEeRd2vou1vcBi17wpQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K_QiIEuY6MJY11R-khfgkA.png" /></figure><p><strong>Step 15: Start the Apache service</strong><br>After the installation is complete, <strong>start</strong> the Apache service by running the following command:</p><p>bash<br><strong>Copy code</strong></p><p>sudo systemctl <strong>start</strong> http</p><p>then to <strong>enable</strong></p><p>run command systemctl <strong>enable</strong> http</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*EkT0vh30deW4UYhUInsajw.png" /></figure><p>To ensure that your IP address is running and properly configured on Fedora, you can follow these steps:</p><ol><li>Open a terminal: Search for “Terminal” in your Fedora applications menu and open it.</li><li>Check the IP address: Run the following command to display network interface information and IP addresses:</li></ol><p>That’s it! You have successfully created a t2.micro EC2 instance with Apache web server. You can now start hosting your website or web application on this instance. Remember to properly secure your server and configure any necessary firewall settings to ensure the security of your web server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QiX2JeYYkbkDHJmjTnUeGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mCSLRzT0OcW3Z5zS" /><figcaption>Photo by <a href="https://unsplash.com/@mrthetrain?utm_source=medium&amp;utm_medium=referral">Joshua Hoehne</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you want to take it further you can use do ADVANCED option</p><ol><li>Make an Amazon Machine Image using the instance you created earlier.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jWI-N44H__QretNa3BsQzw.png" /></figure><ol><li>Launch the instance and verify you are able to reach your web server from the newly created EC2 instance.</li><li>Verify that your new IP Adress works</li></ol><p><a href="http://18.205.163.50/"><strong>http://18.205.163.50/</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*coqreSofr3ynGK8DBaU4GA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74a05453322a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux… What’s Happening ?]]></title>
            <link>https://medium.com/@thomas.erikaj/linux-whats-happening-577bc091dd3e?source=rss-6b453562aaea------2</link>
            <guid isPermaLink="false">https://medium.com/p/577bc091dd3e</guid>
            <category><![CDATA[directors]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[permission]]></category>
            <category><![CDATA[group-permissions]]></category>
            <dc:creator><![CDATA[Erika Thomas]]></dc:creator>
            <pubDate>Mon, 12 Jun 2023 21:45:02 GMT</pubDate>
            <atom:updated>2023-06-12T21:45:02.209Z</atom:updated>
            <content:encoded><![CDATA[<h3>Linux… What’s Happening ?</h3><p>Setting Up User and Group Permissions in Linux: Organizing Directories and Access Control</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hrxTqVRevkSOkEKW.jpg" /></figure><h3>DIRECTORY, PERMISSIONS, USER</h3><p>Introduction: In this tutorial, we will explore how to set up user and group permissions in Linux to organize directories and control access to them. By following a series of commands, we will create three directories — Development, Operations, and Analytics — and populate them with blank dummy files. We will also create three groups — Developers, Operations, and Data Analysts — and assign each group exclusive access to their respective directory. Lastly, we will create three users — Jess Waller, Blake Dorsey, and Joey Ewart — and ensure they have appropriate access to their designated directories.</p><p>Let’s get started!</p><p><strong>Step 1: Creating Directories and Adding Dummy Files: To create the directories, Development, Operations, and Analytics, use the following commands:</strong></p><p><strong>mkdir Development<br>mkdir Operations<br>mkdir Analytics</strong></p><p>Now, let’s add dummy files to each directory. Execute the following commands:</p><p><em>touch Development/file1.txt<br>touch Development/file2.txt<br>touch Development/file3.txt</em></p><p><em>touch Operations/file1.txt<br>touch Operations/file2.txt</em></p><p><em>touch Analytics/file1.txt<br>touch Analytics/file2.txt<br>touch Analytics/file3.txt</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*qnaQjlDTsG6VmEXYTy4nug.png" /></figure><p><strong>Step 2: Creating Groups: We will now create three groups — Developers, Operations, and Data Analysts — using the following commands:</strong></p><p><em>sudo groupadd Developers<br>sudo groupadd Operations<br>sudo groupadd “Data Analysts”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*tpRSAtZ3FH2eCw1e3Uk0Gw.png" /></figure><p><strong>Step 3: Assigning Directory Permissions: Next, we need to assign appropriate permissions to the directories, granting each group access to their respective directory. Execute the following commands:</strong></p><p><em>sudo chown -R :Developers Development<br>sudo chown -R :Operations Operations<br>sudo chown -R :”Data Analysts” Analytics</em></p><p><em>sudo chmod 400 Development<br>sudo chmod 400 Operations<br>sudo chmod 400 Analytics</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*qnaQjlDTsG6VmEXYTy4nug.png" /></figure><p><strong>Step 4: Creating Users and Assigning Groups: Now, let’s create the three users — Jess Waller, Blake Dorsey, and Joey Ewart — and assign them to their respective groups. Run the following commands:</strong></p><p><em>sudo useradd -m -G Developers -s /bin/bash -c “Jess Waller” jwaller<br>sudo useradd -m -G Operations -s /bin/bash -c “Blake Dorsey” bdorsey<br>sudo useradd -m -G “Data Analysts” -s /bin/bash -c “Joey Ewart” jewart</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*O8FUoMq_ZufPi62-tX0Wxg.png" /></figure><p><strong>Step 5: Verifying User Access: To ensure that the users can only see their respective directories and access the files within, switch to each user account and verify their access. Execute the following commands:</strong></p><p><em>su — jwaller<br>ls -l</em></p><p><em>su — bdorsey<br>ls -l</em></p><p><em>su — jewart<br>ls -l</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/561/1*VJ-8zYj5pAMfb_ybnrSjhA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*TeRxH9KMFyJV9gnjMOnGYg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*lkpsJVO1hjs8fzgZ8MJMBg.png" /></figure><h4><strong>Conclusion</strong>: Congratulations! You have successfully organized directories and implemented user and group permissions in Linux. Each user now has access to their designated directory, while being restricted from others. By understanding the concepts of ownership, groups, and permissions, you can effectively control access to files and directories on your Linux system.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LtX_9JfTyD87iwwN" /><figcaption>Photo by <a href="https://unsplash.com/@ianstauffer?utm_source=medium&amp;utm_medium=referral">Ian Stauffer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>Happy organizing and securing your file system!</strong></h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=577bc091dd3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS EC2 CentOS server]]></title>
            <link>https://medium.com/@thomas.erikaj/aws-ec2-centos-server-d82a4ea458dd?source=rss-6b453562aaea------2</link>
            <guid isPermaLink="false">https://medium.com/p/d82a4ea458dd</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[ec2-instance-connect]]></category>
            <category><![CDATA[ec2-instance]]></category>
            <category><![CDATA[apache]]></category>
            <category><![CDATA[centos]]></category>
            <dc:creator><![CDATA[Erika Thomas]]></dc:creator>
            <pubDate>Mon, 05 Jun 2023 14:22:12 GMT</pubDate>
            <atom:updated>2023-06-05T14:22:12.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tm962IRzfwEwFRF_T4iaKg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*QmVGZhr6VzzQgC-iU4Ulsw.jpeg" /></figure><p>What is APACHE ??</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J6TvN8Tw5ao5qhj-MgAU0g.jpeg" /><figcaption><strong>Web server is software that responds to the request for web resources. Apache HTTP Server is an open-source, cross-platform web server that was released under the license of Apache 2.0</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/224/1*E5IboGsSVW8SVRA5w1_55w.png" /></figure><h3>Setting Up an Apache Server on EC2 Instance in AWS: A Step-by-Step Guide</h3><p>Welcome to the step-by-step guide on how to create and configure an Apache server on an EC2 instance in AWS. This documentation will help you set up a robust web server to host your website or web application. By following these instructions, you’ll have your Apache server up and running in no time.</p><h3><strong>Section 1: Launch an EC2 Instance</strong></h3><p><em>Subsection: Create an AWS account (if not already done).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DLzw6TVCKqqmB0gyIH4mdQ.png" /></figure><p><em>Subsection: Launching a new EC2 instance.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/278/1*bg81elX7q7RNYph0N8rcgQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*wFXElNbjjNHZTY8iO82zeg.png" /></figure><p><strong>Step 1: Select the desired region.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/344/1*YXrxzHqpk11AgrGybpSCfw.png" /></figure><p><strong>Step 2: Choose the appropriate Amazon Machine Image (AMI).</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*qm7jKIEe-3bk77kVE3nvow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hnishmOlHNxdwcBmvsyhGw.png" /></figure><p><strong>Step 3: Select the instance type.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*NgC5IpDTVwH8DMvfqwt17A.png" /></figure><p><strong>Step 4: Configure instance details (subnet, security group, etc.):</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*Zk7fB_sZVrmRnh7b9O0Iow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*i7n2wdsN_lhsh8-b87OrZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*6fw_5XunfwxK3L3uf2jvfQ.png" /></figure><p><strong>Step 5: Add storage if necessary.</strong></p><p><strong>Step 6: Configure security settings (SSH key pair, security group rules).</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*VGzi1jC2JPdN7GOIwQUsag.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/227/1*8dAn559JUpYSMYA1S4ZACQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*pMvAWu-4zoRynEnnXdHJXA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/1*DoOda8fzSs1Nchi6Qi-ISQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/1*Kf_vyjM8rjk4JHbqR-6Yow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*6fw_5XunfwxK3L3uf2jvfQ.png" /></figure><p><strong>Step 7: Review and launch the EC2 instance.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*BBBYbiqT0vlLt9xVjMUz7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/222/1*g5EnkJWXW4CzQ6Bj2RrU7g.png" /></figure><h3>Section 2: Connect to the EC2 Instance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*NXGfRDWgA8LOJfBGGgkasA.png" /></figure><p><em>Subsection: Obtain the public IP address of the EC2 instance.</em></p><p><em>Subsection: Connect to the EC2 instance via SSH.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*JPbqMgUvTq_DI0FA_kjoBQ.png" /></figure><p><strong>Step 1: Use an SSH client (e.g., Terminal, PuTTY) to establish a connection.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8XbQsCy7A5uZx-JnY2LBpA.png" /></figure><p><strong>Step 2: Log in with the SSH key pair.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*df8Syhaxdi8JjJb-cXWFLg.png" /></figure><p><strong>Step 3: Verify the successful connection.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*dVKMWsNkOBvBM-BiFti8KA.png" /></figure><h3>Section 3: Installand Configure Apache Server</h3><p><em>Subsection: Updating the package repository and installing Apache.</em></p><p><em>Subsection: Configuring the Apache server.</em></p><p><em>Subsection: Updating the package repository and installing Apache.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*z9_6QNj07d7MjH3teFtK8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i5SJdTC3g99Ywl8WuwpD9w.png" /></figure><p><em>Subsection: Configure the Apache server.</em></p><p><strong>Step 1: Edit the Apache configuration file.</strong></p><p><strong>Step 2: Configure virtual hosts for multiple websites, if desired.</strong></p><p><strong>Step 3: Enable necessary modules (e.g., mod_rewrite, mod_ssl).</strong></p><p><strong>Step 4: Test the Apache configuration for any errors.</strong></p><p><strong>Step 5: Restart the Apache service.</strong></p><p><strong>Section 4: Test the Apache Server</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wo0c4KCbbRmb-QL49S_hGA.png" /></figure><p><em>Subsection: Verify the Apache server installation.</em></p><p><strong>Step 1: Open a web browser and access the EC2 instance’s public IP address.</strong></p><h3><a href="http://52.73.238.99/"><strong>http://52.73.238.99/</strong></a></h3><p><strong>Step 2: Check for the default Apache welcome page.</strong></p><p><strong>Step 3: Test additional configuration or virtual hosts.</strong></p><p>Conclusion:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*zgc2YNm7KOoZV89qo6tl9w.png" /></figure><blockquote>Congratulations! You have successfully created and configured an Apache server on an EC2 instance in AWS.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*kypVxVN2o9h5EYgsntfKhw.jpeg" /></figure><p>Now you can start hosting your website or web application. Remember to customize the Apache server’s configuration as per your specific requirements and security considerations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d82a4ea458dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Step-by-Step Guide to Building an S3 Bucket in AWS and Uploading a Static Website]]></title>
            <link>https://medium.com/@thomas.erikaj/a-step-by-step-guide-to-building-an-s3-bucket-in-aws-and-uploading-files-586ce49f4eb8?source=rss-6b453562aaea------2</link>
            <guid isPermaLink="false">https://medium.com/p/586ce49f4eb8</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[s3-bucket]]></category>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[how-to-build-a-s3]]></category>
            <dc:creator><![CDATA[Erika Thomas]]></dc:creator>
            <pubDate>Tue, 16 May 2023 21:28:49 GMT</pubDate>
            <atom:updated>2023-05-18T17:28:27.078Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>Introduction: What is AWS ?</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*dH77zb6_c0BtL7tMIG12UA.png" /></figure><p><strong>Amazon Simple Storage Service (S3) is a widely used cloud storage solution provided by Amazon Web Services (AWS). It offers secure, scalable, and highly available object storage for storing and retrieving any amount of data from anywhere on the web. In this article, we will walk you through the process of building an S3 bucket in AWS and uploading files to it.</strong></p><p><strong>Step 1: Create an S3 Bucket</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gh41bt6Dik8LIwYUpahJWg.png" /></figure><ol><li>Log in to your AWS Management Console and navigate to the S3 service.</li><li>Click on the<strong><em> “Create bucket” </em></strong>button.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oKdzajtKMO1XYTUNjrFY3Q.png" /></figure><p>Provide a<strong> unique name</strong> for your bucket. AWS S3 bucket names must be globally unique.</p><ol><li>Select the region where you want your bucket to be located. Consider choosing a region closest to your target audience for better performance.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0kUvbVI8jarD8sGrNuURw.png" /></figure><ol><li>Configure optional settings like versioning, logging, and tags as per your requirements.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hbyBNKO1gnMggzVruE2pGA.png" /></figure><ol><li>Click on the “Create bucket” button to create your S3 bucket.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/411/1*5zSFlbCei9Q5r-mRJjcmGQ.png" /></figure><p><strong>Step 2: Configure Bucket Permissions</strong></p><ol><li>Select the newly created bucket from the S3 bucket list.</li><li>Click on the “Permissions” tab and then select “Bucket Policy” from the sub-menu.</li><li>Create a bucket policy to define who can access your bucket and what actions they can perform. You can use the AWS Policy Generator or write the JSON policy manually.</li><li>Save the bucket policy.</li></ol><p><strong>Step 3: Upload Files to the S3 Bucket</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tvUiJFf-R1xwi0FrUMlZTg.png" /></figure><ol><li>Within the S3 bucket, click on the “<strong>Upload</strong>” button.</li><li>You can either choose to upload files directly or upload a folder containing multiple files.</li><li>Select the files you want to upload from your local machine and click on the “Open” button.</li><li>By default, the files will be uploaded to the root of your bucket. If you want to organize your files into folders, you can specify a key prefix in the “Set Details” section.</li><li>You can configure advanced options like server-side encryption, access control permissions, and metadata as per your requirements.</li><li>Click on the “Upload” button to start uploading your files to the S3 bucket.</li></ol><p><strong>Step 4: Verify Uploaded Files</strong></p><ol><li>Once the upload is complete, you will see the uploaded files listed within the S3 bucket.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_wPAwiysqqa1T1PjR2lUFw.png" /></figure><ol><li>You can click on the file names to access and manage individual files.</li><li>To make your files publicly accessible, select the file, click on the “Actions” button, and choose “Make public” or configure appropriate bucket policies.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iRT38MP-Vx-5GcsZCAHioA.png" /></figure><p><strong>Step 5</strong>: <em>Enable Static Website Hosting</em></p><p>Once your bucket is created, select the bucket from the S3 dashboard.<br>Click on the “Properties” tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*kZtOCaO68beZ4OHvrF09pQ.png" /><figcaption>Properties Tab</figcaption></figure><p>Scroll down to the “Static website hosting” section and click on the “Edit” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8PY30Koq_qaGEgCmQjG6qQ.png" /><figcaption>Static Hosting</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YBCsN90HkTLui-I0kRCB_Q.png" /><figcaption>Edit Static Hosting</figcaption></figure><p>Select the option “Use this bucket to host a website.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*mcid3YGKrZw2HeWj0FYw3Q.png" /><figcaption>Enable and select Host a static website</figcaption></figure><p>In the “Index document” field, enter the filename for your main web page (e.g., “index.html”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*9R4DIAim8P4ZvkSH7DbI6A.png" /><figcaption>Enter the filename</figcaption></figure><p>Optionally, you can specify a custom error document if you want.<br>Click on the “Save changes” button.<br>Step 3: Upload Website Files to the Bucket</p><p>Go back to the main dashboard of your bucket.</p><p>Click on the “Upload” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*A1nN3W_WgjqGhzLj7bd_7g.png" /></figure><p>Click on the “Add files” button and select the HTML, CSS, and JavaScript</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/110/1*973zmpmlWgidXKAg_R6tSQ.png" /></figure><p>files that make up your website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/251/1*kwgCkeV3y4sTOdFVNHRirg.png" /></figure><p>Once you have added all the files, click on the “Upload” button to start the upload process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MYHugbzms76QJpUN" /><figcaption>Photo by <a href="https://unsplash.com/@ptrc?utm_source=medium&amp;utm_medium=referral">Piotr Cichosz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Step 4: Configure Bucket Permissions</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*VCbwKvE4x3se86xz9R7aVw.png" /></figure><p>Select your bucket from the S3 dashboard.<br>Click on the “Permissions” tab.<br>Scroll down to the “Bucket policy” section and click on the “Edit” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ixAc3pL-bMQbjKUxuGwlg.png" /></figure><p>In the bucket policy editor, enter the following policy, replacing “your-bucket-name” with the actual name of your bucket:<br>json<br>Copy code</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*3VPeZ_2UwTZUor_Vpsw0yQ.png" /></figure><p>Click on the “Save changes” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/175/1*W7SOjgq0UdHZF1K2A2D_Uw.png" /></figure><p>Step 5: Make Your Website Publicly Accessible</p><ol><li>Select your bucket from the S3 dashboard.</li><li>Click on the “Properties” tab.</li><li>Scroll down to the “Static website hosting” section.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*aDYpgp6XzNpYx6y7NobvBA.png" /></figure><p>4. Copy the Endpoint URL listed under the “Endpoint” field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*TZpP1yL4GLdO9iqnqh51zQ.png" /></figure><p>5. Open a web browser and paste the Endpoint URL. You should be able to access your website now.</p><p><a href="http://erikabucketproject.s3-website-us-east-1.amazonaws.com/">Level Up Bank</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*86s8R71yXawIQbjOv00O-Q.png" /><figcaption>Static Website</figcaption></figure><p><strong>Conclusion: </strong>Congrats you did it</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y0DlSK0sbhkh6CNc" /><figcaption>Photo by <a href="https://unsplash.com/@deandre?utm_source=medium&amp;utm_medium=referral">De&#39;Andre Bush</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>That’s it! You have successfully built an S3 bucket with a static website. Make sure to test your website thoroughly to ensure everything is working as expected.</strong></p><p><em>Building an S3 bucket in AWS and uploading files is a fundamental process for leveraging Amazon’s powerful cloud storage service. By following the steps outlined in this guide, you can create an S3 bucket, configure its permissions, and seamlessly upload your files to the bucket. With the flexibility and scalability offered by S3, you can store and retrieve data efficiently, making it an essential component for various applications and workflows in the AWS ecosystem.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=586ce49f4eb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first week !]]></title>
            <link>https://medium.com/@thomas.erikaj/my-first-week-288b4c8a4cf2?source=rss-6b453562aaea------2</link>
            <guid isPermaLink="false">https://medium.com/p/288b4c8a4cf2</guid>
            <dc:creator><![CDATA[Erika Thomas]]></dc:creator>
            <pubDate>Tue, 16 May 2023 21:19:24 GMT</pubDate>
            <atom:updated>2023-05-16T21:19:24.032Z</atom:updated>
            <content:encoded><![CDATA[<h3>My first week !</h3><p>I love Level Up in Tech</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*cyZQQpHINyhc28fwk-iPig.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=288b4c8a4cf2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>