<?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 Mikey McKelvey on Medium]]></title>
        <description><![CDATA[Stories by Mikey McKelvey on Medium]]></description>
        <link>https://medium.com/@mikeyxmck?source=rss-b4bd5b4a00a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*delAnJl3POBpAk7Ye2cCjg.png</url>
            <title>Stories by Mikey McKelvey on Medium</title>
            <link>https://medium.com/@mikeyxmck?source=rss-b4bd5b4a00a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:29:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mikeyxmck/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[Linux User and Group Management on AWS EC2 (RBAC with /srv)]]></title>
            <link>https://medium.com/@mikeyxmck/linux-user-and-group-management-on-aws-ec2-rbac-with-srv-8758e4580bdb?source=rss-b4bd5b4a00a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8758e4580bdb</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-ec2]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Mikey McKelvey]]></dc:creator>
            <pubDate>Thu, 05 Feb 2026 02:23:58 GMT</pubDate>
            <atom:updated>2026-02-05T02:23:58.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q6oSQzpxqpbEodOc-pN51A.png" /></figure><p>Project Overview:<br>With LevelUp Bank continuing to grow, maintaining a secure and well-structured Linux environment is essential to protecting internal data and supporting daily operations. With teams in Development, Operations, and Data Analytics, the organization requires a user and permission model that enforces strict separation of access while remaining scalable and efficient. <br>The project focuses on implementing role-based access control (RBAC) using native Linux tools.</p><p>Objective: <br>We will ensure that users can access only data relevant to their department, while preventing visibility into or modification of resources belonging to other departments. This will show real-world enterprise environments where incorrect permissions can lead to data leaks, compliance violations, and operational risks.</p><p>Step By Step:<br>In the Linux terminal, you will need to log in as Root. Use the sudo -i command, then confirm you are in root by running whoami. We will use this for all system-level directory and permission changes.</p><p>Next, we will create Shared Directories in<em>/srv</em>. Use the command <em>mkdir -p /srv/Development /srv/Operations /srv/Analytics</em> after that confirm that the directories are created by using the <em>ls -ld /srv/*</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*6hb3oGZ83YF0N8kdT3ZKEQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*HhMaa_XhJOx_2fVkXxxj0A.png" /></figure><p>Then create files for each directory using the <em>touch /srv/Development/devops.txt /srv/Development/devprojects.txt /srv/Development/codes.txt </em>. You will do the same for Operations and Analytics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1j6GRosUm5nNnXCU8vVwVA.png" /></figure><p>We will now use the <em>groupadd </em>command to create groups. The command is as follows: <em>groupadd Developers, groupadd Operations, groupadd Analysts</em></p><p>Then we will assign the group ownership to each directory. using the <em>chown -R </em>command. The command would look like: <em>chown -R : Developers /srv/Development. </em>We will do the same for the other directories. This will set group ownership, not user ownership.</p><p>After that, we will lock down permission to ensure that only group members can read, write, or enter the directory. we will use the command <em>chmod -R 2770 /srv/Development /srv/Operations /srv/Analytics</em><br>Why 2770?<br>2 → setgid(let’s new files inherit the group)<br>7 → full access for owner and group<br>0 → no access for others</p><p>We will create users and assign groups using the follow commands<br><em>useradd -m -s /bin/bash -G Developers jwaller<br>useradd -m -s /bin/bash -G Operations bdorsey<br>useradd -m -s /bin/bash -G Analysts jewart<br></em>After the users are added, you can use the <em>passwd </em>command to set the passwords.</p><p>Linux can also store user metadata. We will need to add more information about the user, and we can do so with the <em>usermod </em>command. it will look as follows: <em>usermod -c “Jess Waller, jwaller@levelupbank.com” jwaller</em></p><p>Finally, we will verify access control and access our user account using the <em>su — &lt;username&gt; </em>command. Then we will attempt to list the files in the directories, starting with the directory we assigned earlier. <em>ls /srv/Development, </em>we should be able to access it. If we attempt to access directories we did not grant the user permission to, we should get an access denied error when running the ls /srv/Operations command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*TxP1t0V_Vl5neFs07BKcjQ.png" /></figure><p>Overall<br>This project aligns with real-world responsibilities in system administration, DevOps, and infrastructure security, while also providing hands-on experience with Linux permissions, group management, and secure directory design for a business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8758e4580bdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying an Apache Web Server on Linux Using AWS EC2]]></title>
            <link>https://medium.com/@mikeyxmck/deploying-an-apache-web-server-on-linux-using-aws-ec2-c28452024f3c?source=rss-b4bd5b4a00a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c28452024f3c</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[apache]]></category>
            <category><![CDATA[ec2]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Mikey McKelvey]]></dc:creator>
            <pubDate>Tue, 03 Feb 2026 21:11:22 GMT</pubDate>
            <atom:updated>2026-02-03T21:11:22.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJn4pSzAgyMcY17ZQ3WGJw.png" /></figure><p>Project Objective:<br>For this project, the goal was to deploy a publicly accessible Apache web server using an Amazon EC2 instance running Amazon Linux 2. This can mirror a common real-world issue where companies host web services while maintaining secure administrative access.</p><p>Apache was chosen for its stability, flexibility, strong security features, and widespread adoption in enterprise environments. Linux was used as the OS for performance and reliability.</p><p>Environment &amp; Tools Used:<br>-AWS EC2<br>-Amazon Linux 2<br>-Apache HTTP Server<br>-SSH<br>-Linux Command Line<br>-AWS Security Groups<br>-Web browser for validation</p><p>Step By Step:</p><p>Creating the EC2 Instance:<br>Launch an EC2 instance with Amazon Linux 2. During the setup process, I configured a security group with the follow rules:<br>-SSH (Port 22): Restricted it to my personal IP address to prevent unauthorized access<br>-HTTP (Port 80): Allows for public web traffic<br>-HTTPS (Port 443): Allowed for secure web traffic</p><p>Connecting to the Instance:<br>Once the instance was up and running, I connected to it using SSH. This provided secure command-line access to the Linux Server. Which allowed me to manage system updates and install required software.</p><p>Updating the System:<br>Before installing any services I ensure that the system was fully up to date by running the follow command. <em>sudo yum update -y, sudo</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jYTaznwNqHfvNnMbhcJU-g.png" /></figure><p>Installing Apache:<br>After updating the system, i installed the Apache HTTP web server using the following command: <em>sudo yum install httpd -y</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*CDdc-A9xMgxUkxCfNvWsJw.png" /></figure><p>Starting and Enabling Apache:<br>Once Apache was installed i started the service with: <br>-<em>sudo systemctl start httpd<br></em>To ensure Apache would automatically start on system boot, I enabled the service:<br><em>-sudo systemctl enable httpd<br></em>I then verified that Apache was running correctly by checking its status:<br><em>-system status httpd<br></em>The service was active and running, which confirmed that we got a successful installation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vqtX4Kx3g_sbU7AL-Z1Zgg.png" /></figure><p>Verify Public Access<br>To confirm that the web server was accessible over the internet, I copied the public ip address of the EC2 Instance and entered it into the a web browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*3nKQ0y-Wnh8eVnDj7Rse7w.png" /></figure><p>The Apache default test page loaded successfully, confirming that: <br>-Apache was running<br>-The security group rules were correctly configured<br>-The server was publicly reachable</p><p>Takeaways:<br>-I gained hands-on experience deploying a Linux server in AWS<br>-Learned how to securely configure AWS security groups<br>-Installed and managed services using <em>systemctl </em><br>-Successfully deployed and validated a public-facing web server<br>-I was also able to strengthen more of my foundational skills when it comes to cloud and Linux skills.</p><p>Conclusion: <br>The highlights of this project are the core steps required to deploy a web serverin a cloud environment using AWS and Linux. This setups relfects real world practices used in production environments, particularly in industries where security and reliability are critical.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28452024f3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secure Remote Administration and Troubleshooting of EC2 Instances]]></title>
            <link>https://medium.com/@mikeyxmck/secure-remote-administration-and-troubleshooting-of-ec2-instances-04875eb5d53f?source=rss-b4bd5b4a00a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/04875eb5d53f</guid>
            <dc:creator><![CDATA[Mikey McKelvey]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 00:13:35 GMT</pubDate>
            <atom:updated>2026-01-26T00:13:35.100Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*DXShI2jRd1FL6LTMZPfaRw.png" /></figure><p>Project Overview:</p><p>Level Up Corporation needs a secure way to administer cloud servers hosted on AWS remotely. In this foundational project, we deploy a Linux EC2 instance and securely connect to it using SSH, demonstrating secure remote administration in a real-world cloud environment</p><p>Prerequistes: <br>Amazon Management Console</p><p>Benefits:<br>The benefits of this would be security when accessing servers remotely via SSH, which uses key-based authentication and further restricts access based on the creation of a security group.</p><p>Step By Step: <br>Once you log in to your AWS Account, navigate to Amazon EC2 and click Launch. You will enter the instance name. In this demonstration, it will be LvlUpCorpEc2. Then we will choose Amazon Linux for the AMI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qtng35qc8SymnfpJn-gyQQ.png" /></figure><p>Then, create a new key pair. This will allow us to securely connect to our Instance. The name for the key pair will be SCRET_K. Under the Network Settings Tab, we will create a Security Group. Make sure to allow SSH traffic, and, to make it even more secure, we can restrict it to our IP address. This will ensure that only our address can access the instance.</p><p>Once we confirm the security group, we will launch the instance. It will then bring us to the Next Steps, where we will click on Connect to your Instance. This will bring us to different ways to connect. We will us SSH Client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rcro_cqHRRnOWlR6JsBOUg.png" /></figure><p>Open up a Terminal and use the cd (Change Directory) command to go to where the private key file is then you will use the command ssh -i “Private Key” <strong><em>ec2-user@ec2–22–333–444–555.compute-1.amazonaws.com</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8TtM_mltlBQvDpRO36hQw.png" /></figure><p>Once connected, enter the whoami command to confirm you have access.</p><p>Project Conclusion:</p><p>This will demonstrate how we can secure remote administration using AWS EC2 and SSH. By properly configuring key pairs, security groups, and access controls, Level Up Corp can safely manage the Linux servers in the cloud while keeping security risks to a minimum.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04875eb5d53f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hosting a S3 Static Website]]></title>
            <link>https://medium.com/@mikeyxmck/hosting-a-s3-static-website-08ca1a1177c4?source=rss-b4bd5b4a00a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/08ca1a1177c4</guid>
            <category><![CDATA[static-site]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-s3]]></category>
            <dc:creator><![CDATA[Mikey McKelvey]]></dc:creator>
            <pubDate>Mon, 12 Jan 2026 23:13:20 GMT</pubDate>
            <atom:updated>2026-01-13T02:00:44.917Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*G0E59j8-iQppsRzi_Go3Hw.png" /><figcaption>Note: The website was not developed by me. My goal is to configure the S3 bucket and ensure the site functions correctly as a static website.</figcaption></figure><p><strong><em>Project Overview:</em></strong></p><p>Here, I will demonstrate how to host a static website on an Amazon S3 bucket using the AWS Management Console. The goal was to configure an already pre-existing HTML file to be publicly accessible over the internet using S3’s Static Website Hosting feature.</p><p><strong><em>Prerequisites</em></strong>:<br>AWS Management Console</p><p><strong><em>Benefits of Hosting a Static Website on S3:<br></em></strong>One of the benefits of hosting a static website is the cost compared to hosting it on-premises. It is much more cost-effective not only because hardware maintenance is not required but also because S3 charges only for the storage used, and the cost of transferring data is minimal.<br>Another benefit would be scalability, with S3 you are able to increase the traffic without any additional infrastructure changes. <br>The third benefit would be it’s ability to have high availability. S3 can provide that by using multiple availability zones to ensure that the website remains accessible to users at all times.</p><p><strong><em>Step by Step:<br></em></strong>The first step would be to create the Amazon S3 bucket. For this project, we will be naming it lvlupsite.<em> </em>Then you will go to the Properties Tag and scroll down to <strong>Static website hosting.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*VB1mA787A0vACwArCmD-eg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*DxlMUgqVIwwMEQu_Tf55-g.png" /></figure><p>We now need to enable static website hosting. This will allow us to host a website or use it as a redirect request. We will keep the <strong>Hosting Type </strong>to host a static website. Then we have to make sure we specify the name of the HTML file we are using. Then we will click <strong>Save Changes.</strong></p><p>Afterwards, we will head back to the <strong>Objects Tag</strong> and add the HTML File. Then we will head over to <strong>Permissions</strong>, where we will see<strong> Block public access (bucket settings). </strong>We will turn that off. We can edit to choose exactly what we will block and allow, but for now, we will allow all public access. You edit the permissions and confirm them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*mehci894wvchcb-wE80ZQg.png" /></figure><p>Next, we will head over to the <strong>Bucket policy</strong> located right under the <strong>block public access. </strong>Here, we will write the policy in <strong>JSON</strong>, which is what provides us access to the <strong>Objects</strong> in <strong>S3.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*IE_MVqJLS9c4Na5qCHeNxQ.png" /></figure><p><strong><em>Verifying:<br></em></strong>Once we confirm the <strong>JSON </strong>is correct, we can verify that the website URL is working by returning to the <strong>Static website hosting</strong> under <strong>Properties</strong>. There, we can see the <strong>Bucket website endpoint</strong> that holds the link for our website. Copy it and test whether we can access the website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/929/1*3XsyodoAbbWxoaWbZwG4CQ.png" /></figure><p>We are able to access it!</p><p><strong><em>Issues Encountered:</em></strong></p><p>During the process, I attempted to add the HTML file but received an <strong>Unknown Error</strong>. I realized I was inputting the files under the redirection rules instead of simply adding them under the <strong><em>Objects.</em></strong></p><p>Another Issue I encountered was when I was attempting to access the website. I received an <strong>Access Denied</strong> error. Further investigation revealed that I did not have a bucket policy in place to grant public read access. I added it (see above) and was able to access the website afterward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=08ca1a1177c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First Post]]></title>
            <link>https://medium.com/@mikeyxmck/first-post-d75b006831af?source=rss-b4bd5b4a00a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d75b006831af</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Mikey McKelvey]]></dc:creator>
            <pubDate>Mon, 12 Jan 2026 18:48:53 GMT</pubDate>
            <atom:updated>2026-01-12T18:48:53.661Z</atom:updated>
            <content:encoded><![CDATA[<p>This is my first post. I am going to be documenting my journey into the Cloud. Currently focusing on AWS.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d75b006831af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>