<?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 Elijah Victor  on Medium]]></title>
        <description><![CDATA[Stories by Elijah Victor  on Medium]]></description>
        <link>https://medium.com/@elijahvix695?source=rss-35c5c63cb7df------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*MbdruumrZqxFGAWw</url>
            <title>Stories by Elijah Victor  on Medium</title>
            <link>https://medium.com/@elijahvix695?source=rss-35c5c63cb7df------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:09:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elijahvix695/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[Building My First Secure AWS Network with a Bastion Host]]></title>
            <link>https://medium.com/@elijahvix695/building-my-first-secure-aws-network-with-a-bastion-host-59f0e71fc3cc?source=rss-35c5c63cb7df------2</link>
            <guid isPermaLink="false">https://medium.com/p/59f0e71fc3cc</guid>
            <dc:creator><![CDATA[Elijah Victor ]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 22:03:53 GMT</pubDate>
            <atom:updated>2026-10-25T22:03:53.192Z</atom:updated>
            <content:encoded><![CDATA[<p>In this project, I built an AWS network with a public bastion host and a private EC2 instance. My goal was to connect to the private instance from my Fedora computer without exposing that instance directly to the internet. I completed the setup in the Europe (Stockholm) region, eu-north-1, using two Amazon Linux 2023 t3.micro instances.</p><h3>What Is a Bastion Host?</h3><p>A bastion host, also called a jump box, is a server that provides an entry point for accessing servers inside a private network. Instead of giving every server a public IP address, an administrator connects through the bastion.</p><p>In my setup, the bastion had a public IP address, while the private instance had none. I restricted SSH access to the bastion to my own public IP address. The private instance accepted SSH connections only from the bastion’s security group. This reduced the private instance’s exposure to incoming internet traffic.</p><h3>How I Built the Network</h3><p>I started by creating a Virtual Private Cloud with the IPv4 address range 10.0.0.0/16. Inside it, I created a public subnet using 10.0.1.0/24 and a private subnet using 10.0.2.0/24. Both subnets were in the same Availability Zone, eu-north-1a.</p><p>Next, I created an Internet Gateway and attached it to the VPC. I created a public route table containing the existing local route and an additional route sending 0.0.0.0/0 traffic to the Internet Gateway. I associated this table with the public subnet.</p><p>For the private subnet, I created a separate route table containing only the local VPC route. This allowed communication within the VPC without providing general internet access. I did not create a NAT Gateway.</p><p>I then created two security groups. The bastion group allowed inbound TCP port 22 from my public IPv4 address with a /32 prefix. The private group allowed inbound TCP port 22 with the bastion security group selected as its source.</p><p>Afterward, I launched the bastion in the public subnet with a public IP enabled. I launched the private instance in the private subnet with public IP assignment disabled.</p><p>On Fedora, I restricted access to my downloaded private key, loaded it into an SSH agent, and connected to the bastion using ssh -A. From the bastion, I connected to the private instance at 10.0.2.181. Agent forwarding allowed authentication without copying my private key onto the bastion.</p><h3>Problems I Encountered</h3><p>One mistake I made was adding SSH under outbound rules instead of inbound rules. I corrected this after understanding that inbound rules control connections entering an instance, while outbound rules control connections leaving it.</p><p>I also encountered command errors when checking the instances’ IP addresses. I entered hostname-I and later misspelled hostname. The correct command was hostname -I. Running it successfully confirmed which instance I was connected to.</p><h3>What I Learned</h3><p>This project helped me understand how routing, security groups, and SSH authentication work together. I learned that naming a subnet “public” does not make it public; its routing configuration matters. Successfully reaching the private instance through the bastion showed me how administrators can manage private servers through a controlled entry point.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f0e71fc3cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>